Using an iRule to respond with a 500 Internal Server Error message

Question

Hi,&nbsp;
We have a customer error page setup to serve a nice neat error page when various violations are triggered however the JSON applications don't like this as they are not expecting html. What I would like to do is implement an iRule based on any identifiable data such as a header, to respond with a 500 error. For the moment I am just working on the main idea of serving the 500 rather than the custom error however what I have is not working. If someone can review what I have below and let me know why this is ignored and the custom error continues to load, that would be awesome. Thank you.&nbsp;
when HTTP_RESPONSE { &nbsp;
        if {[HTTP::header value Connection] contains "close"}{ &nbsp;
             HTTP::respond 500 content "Internal Server Error"
         } &nbsp;
}&nbsp;

yann_desmarest · Answer

Hi,&nbsp;
Try to use Close instead of close&nbsp;
Or&nbsp;
Use&nbsp;
if {[string tolower [HTTP::header value Connection]] contains "close"}{ &nbsp;

yann_desmarest_ · Answer

Hi,&nbsp;
Try to use Close instead of close&nbsp;
Or&nbsp;
Use&nbsp;
if {[string tolower [HTTP::header value Connection]] contains "close"}{ &nbsp;

saidshow_251381 · Answer

Hi Yann, thank you for the prompt reply. I have tried both of the suggestions however neither worked for me.

saidshow_251381 · Answer

Hi Yann, thank you for the prompt reply. I have tried both of the suggestions however neither worked for me.

yann_desmarest_ · Answer

Ok, that's there is no Connection:Close header, you need to use another header to identify errors. Maybe HTTP::status

Forum Discussion

Recent Discussions

Errors with AS3 3.56.0 with F5 17.5.1.6

F5 ASM/AWAF – violations logged but no learning suggestions generated

F5 VELOS Backplane Inter-Tenants Communication

migrate from serie I to R. Cluster LTM-GTM

Best Practice guide for enabling Attack signature In BIG-IP ASM

Related Content

Rate limiting WebSocket messages for Agents

Load Balancing TCP TLS Encrypted Syslog Messages

TCP Internals: 3-way Handshake and Sequence Numbers Explained

Performance optimalization of message based load balancing.

Massive DDoS, DanaBot Dismantled, Scraped Discord Messages and Signal Blocks Windows Recall