OK, so far so good except for just one of the URIs: the /scan.
I'm running ieHTTPHeaders to watch the header traffic in IE (shown below).
When I enter http://newurl.ourdomain.com:8052/webapp, everything looks fine and ieHTTPHeaders shows this:
GET /webapp HTTP/1.1
Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, /
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; chromeframe/30.0.1599.101; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Accept-Encoding: gzip, deflate
Host: iww.lims-minerals.bureauveritas.com:8052
Connection: Keep-Alive
Cookie: s_vi=[CS]v1|292E1112051D385A-40000103A000D0CD[CE]
HTTP/1.1 302 Found
Cache-Control: private
Content-Type: text/html; charset=utf-8
Location: /webapp/Account/LogOn?ReturnUrl=%2fwebapp
Server: Microsoft-IIS/7.5
X-AspNet-Version: 4.0.30319
X-Powered-By: ASP.NET
Date: Thu, 17 Oct 2013 15:58:14 GMT
Content-Length: 162
However, when I try the /scan URI, it looks like I'm getting redirected (by the server I guess?) to the old URL somehow and then IE ends up going straight to the web server using the old URL. ieHTTPHeader info when hitting that link:
GET /scan HTTP/1.1
Accept: application/x-ms-application, image/jpeg, application/xaml+xml, image/gif, image/pjpeg, application/x-ms-xbap, /
Accept-Language: en-US
User-Agent: Mozilla/4.0 (compatible; MSIE 7.0; Windows NT 6.1; WOW64; Trident/4.0; chromeframe/30.0.1599.101; SLCC2; .NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0; .NET4.0C; .NET4.0E; InfoPath.3)
Accept-Encoding: gzip, deflate
Host: http://newurl.ourdomain.com:8052
Connection: Keep-Alive
Cookie: s_vi=[CS]v1|292E1112051D385A-40000103A000D0CD[CE]
HTTP/1.1 301 Moved Permanently
Content-Type: text/html; charset=UTF-8
Location: http://currenturl.olddomain.local/scan/
Server: Microsoft-IIS/7.5
X-Powered-By: ASP.NET
Date: Thu, 17 Oct 2013 15:57:09 GMT
Content-Length: 150
Anything I can write into the iRule to keep that redirect from coming all the way back to my client browser and make the F5 receive that and handle it itself so the client browser just maintains its http session to the new hostname on port 8052 with /scan?