For more information regarding the security incident at F5, the actions we are taking to address it, and our ongoing efforts to protect our customers, click here.

Forum Discussion

oshaughnessy_19's avatar
oshaughnessy_19
Icon for Nimbostratus rankNimbostratus
Sep 10, 2015

Try it with 

curl
from a shell and see if you get the Location header you're expecting:

curl -ski -o- http://qa.client.abc.com

You should see the HTTP response header, then the new location:

HTTP/1.0 301 Found
Location: https://qa.client.800abc.com
Server: BigIP
Connection: Keep-Alive
Content-Length: 0

If you get something else, it might explain strange behavior from Chrome. If you get something like the above, I think it's working correctly.