Forum Discussion
tarsier_90410
Nimbostratus
Oct 17, 2011HTTP::respond - bug or improper use?
When using HTTP::respond 302 Location "https://<...>" in the HTTP_RESPONSE when the server also issued a 302, the LTM's 302 does not appear to work and the client receives the location specified by th...
Michael_Yates
Nimbostratus
Oct 17, 2011LOL. I got a good laugh out of that. No wonder it worked so well 🙂
There is no status value in the HTTP::header, you will need to use [HTTP::status].
If you wish to see your headers use this iRule to verify:
when HTTP_REQUEST {
set LogString "Client [IP::client_addr]:[TCP::client_port] -> [HTTP::host][HTTP::uri]"
log local0. "============================================="
log local0. "$LogString (request)"
foreach aHeader [HTTP::header names] {
log local0. "$aHeader: [HTTP::header value $aHeader]"
}
log local0. "============================================="
}
when HTTP_RESPONSE {
log local0. "=============================================" foreach aHeader [HTTP::header names] {
log local0. "$aHeader: [HTTP::header value $aHeader]"
}
log local0. "============================================="
http://devcentral.f5.com/wiki/iRules.LogHttpHeaders.ashx
}
Help guide the future of your DevCentral Community!
What tools do you use to collaborate? (1min - anonymous)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
