Forum Discussion

Historic F5 Account

May 05, 2006

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...

Historic F5 Account

Jan 07, 2015

I had a customer run into this, where we found the newer browsers performed TCP Keep-Alives that would reset the TCP idle timeout every 10~45 seconds. I poked around and couldn't get the Connection: Keep-Alive header removed or replaced, so I ended up not using the built in HTTP::redirect, and instead simply used:

when HTTP_REQUEST {
 if { [HTTP::uri] contains "secure"}
 {
       HTTP::respond 302 conent {
Location: https://secure.company.com
Server: BigIP
Connection: Close
Content-Length: 0

       }
       return
  }
}