Forum Discussion
Error: read ECONNRESET error while using Postman for API calls after change to irule
- Aug 15, 2022
Hi krisnaseechurn, the HTTP::redirect command is used a couple of times in your iRule.
It´s best practice, to use a "return" command afterwards and perhaps an "event disable" command to prevent the iRule from further execution.
Personally I´m trying to avoid the HTTP::redirect. Instead I prefer to use HTTP::respond because it´s providing very granular control about the exact status code (maybe you prefer a 301 instead of 302?). It also allows to add a Connection Close header. Along with an "event disable" command followed by a "return" you will definitely avoid further execution of the iRule event where the command was fired.
For debugging it would help to force an unwanted redirect and monitor the /var/log/ltm for log entries and TCL errors/warnings:
tail -f /var/log/ltm
- Aug 16, 2022
thanks for all the input..
the issue was it was missing an !
if { !([HTTP::status]=="500") && \
Hi krisnaseechurn,
Can you use parentheses( ) instead of braces{ } in if condition?
when HTTP_RESPONSE {
if { [HTTP::status] == 404 && ([HTTP::header] contains "Content-Type:application/json" || [HTTP::header] contains "Content-Type:application/xml" || [HTTP::header] contains "Content-Type:application/problem+json") } {
set irule "Irule_Catch_404"
...
Recent Discussions
Related Content
* Getting Started on DevCentral
* Community Guidelines
* Community Terms of Use / EULA
* Community Ranking Explained
* Community Resources
* Contact the DevCentral Team
* Update MFA on account.f5.com