Forum Discussion
Deb_Allen_18
May 05, 2006Historic F5 Account
Redirect sends "Connection: Keep-Alive" header
Using a basic HTTP redirect statement: if { blah }{
HTTP::redirect https://$host:$newport[HTTP::uri]
return
}
we're seing an HTTP 1.0 response with a Keep-Alive header, even though the cl...
Deb_Allen_18
May 05, 2006Historic F5 Account
Customer says they are seeing the connection kept alive on the BIG-IP end, closing after the timeout when the client never sends another request.
HTTP::header insert Connection Close
and HTTP::header replace Connection Close
and HTTP::header remove Connection
all affect the inbound header with no effect on the BIG-IP responseIt seems logical that insert / replace / remove can't affect the HTTP::redirect command after it's been issued. Placing the header remove command in HTTP_RESPONSE also didn't work, I'm assuming because that is triggered by a server response, and with a redirect, there is none.
HTTP::respond 302 Location http://www.google.com/ Connection Close
results in both a Connection: Keep-Alive header and a Connection: Close header.We'd also like to modify the Server: header in the redirect, if possible, to something other than "BIG-IP"...
thanks!
/deb
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