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...
bl0ndie_127134
May 05, 2006Historic F5 Account
NOTE: Big IP will send a close only if the client sends a non keep alive request. Why don't you set the idle timeout to a small value after you send the redirect. That way the client can re-use the connection if it chooses to do so and the connection won't linger too long if it doesn't.
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
