Forum Discussion
Jason_Reed_4703
Jan 07, 2015Historic F5 Account
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
}
}
- Georgi__Joe__StDec 22, 2015AltostratusI think you should use: HTTP::respond 302 noserver -reset Connection close Location https://google.com