Forum Discussion
brettbeggs_1177
Apr 08, 2010Nimbostratus
Thanks Aaron.
I ended up having to make one little tweak, adding "https://" to the response code to get it sent over to the correct place.
Send a redirect with the third to last field from the requested host prepended to .mydomain.com
HTTP::respond 301 Location "https://[lindex $host_list [expr {[llength $host_list] -3}]].mydomain.com"
The problem now seems to be that the redirect isnt taking place before the request hits the virtual server. This is causing a certificate error to pop up. Once you add the exception and advance past it, the redirect works like a champ. I guess on some level that makes sense. The request has to hit the virtual server before it processes the iRule, but in doing so, causes the certificate exception.
When monitoring the logs, nothing gets logged until after you accept the certificate warning.