Wingate 302 redirect timeout and delays

[aperia]

I am running Wingate 8.2.1.4711 and have narrowed my current woes down to Wingate not handling 302 HTTPS redirects from our load balancer properly. I can replicate this issue every time in IE9. If I hit one of our sites on our load balancer via HTTP, the redirect to HTTPS either times out or takes 2 to 3 minutes to complete. If I call the site by HTTPS it is immediate. This issue does not show up if we bypass the proxy and go straight to the internet or the load balancer VIPs. Caching is disabled on my proxy server.

[adrien]

Hi

sounds like there may be some issue with the 302 message from the load balancer that makes WinGate think it's not completed.

Can you do a packet capture between WinGate and the load balancer and capture the 302 redirect message?

Regards

Adrien

[aperia]

I've done some Wiresharking and see that it simply makes requests and sits there for a couple minutes before getting the SSL change cipher spec handshake at which point it connects. I've also done more testing and have found that A) this only affects IE, B) it is only reproducible via IE using either the public IP or URL, C) internal load balanced IP addresses are not affected and D) no other browser exhibits this behavior.

So, Firefox and Chrome both will accept and follow the 302 HTTP redirect to HTTPS immediately with no lag using either the public IP or URL. IE will instantly redirect to HTTPS only when using the internal load balancer IP address or by typing in https://url. Otherwise, browser makes a successful HTTP request to Wingate -> Wingate gets '302 moved temporarily' -> browser spins for 2 minutes with no errors and then displays the HTTPS website

This behavior is only when going through Wingate and only with IE. So, does IE have some issue with Wingate? Really strange.

[adrien]

Hi

you'll probably find on closer inspection of the capture issues around timings and TCP RST, or a missing response header in the 302 (or some dodgy content length header)

Something that makes WinGate think the message is not yet complete, until the connection times out then your client is unstuck.

Can we please look at the capture file?

Send in to support@wingate.com

Regards

Adrien