Forum Discussion
Roman_80473
Nov 29, 2011Nimbostratus
Redirect to another URL from inside HTTP::REQUEST after timeout detected
Hi guys,
I have setup the timer using the 'after' command inside HTTP_REQUEST which I then cancel in HTTP_RESPONSE. I detect timeout and take node out of the mix. I then need to redirect req...
Roman_80473
Nov 30, 2011Nimbostratus
Hi Michael,
Thank you very much for looking into my messy rule. Yes, you're abs right, and I do need a lot of cleaning to do. I will as soon as I get it working, I promise.
As far as the url, this is what I see in the logs (masking sensitive data):
Rule Smart_LB_Rule : In lb_selected, server is server.ip.address:8001 ...
Rule Smart_LB_Rule : *** Timeout after 15000 ms ***
Rule Smart_LB_Rule : 1. Taking node server.ip.address:8001 out of the mix ...
Rule Smart_LB_Rule : 2. Redirecting to http://domain_name.company_name.com/controller/?source=ltm&action=restart&host=server.ip.address&service=/bad/&port=8001&name=&cause=no_response_from_server_after_15000_ms&postBack=http://domain_name.company_name.com/bad/
TCL error: Smart_LB_Rule - Illegal argument. Can't execute in the current context. (line 1) invoked from within "HTTP::redirect $theUrl "
The url is valid, and if I put it in the browser, it works just fine. It also works (the HTTP::redirect $theUrl command) from inside both LB_FAILED and HTTP_RESPONSE events (as I've described to nitass). I have a sneaky suspicion it's the "after" timer that is giving me a trouble.
Thank you,
Roman
Recent Discussions
Related Content
DevCentral Quicklinks
* 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
Discover DevCentral Connects