WinGate 7 some https-Redirects dont work..
Jun 21 13 1:56 am
Hi folks,
We use Wingate in all our Locations and it work fine but in some cases we get strange errors.
Some Pages did not work correctly that means for example if i try to login @flickr Page the redirect to the Login Page did not work.
The most other https-pages work fine, f.e. amazon, ebay.
If i change the configured proxy-server (other product - not WinGate) the login page works fine.
some facts:
- WinGate connect via upstream proxy to the internet
- Install a new "out of the Box" installation (Version 7.3.1.3535)
- for test - only configure the upstream proxy
In the Activity-Tab i can see the CONNECT
but the Page did not load...
i got ... "the connection was interrupted"
In the *global.log (with Debug-Level) i only see that..
So the Client recieved the Status 302 and redirect to login.yahoo.com:443, but nothing happend..
In the sample Policy "SSL connect handler" the https-Request with Port 443 are Allowed at the end - if i switch "RestrictSSLPorts to "false" under "Data" ... the same - login page did not load :(
Some idea ? :(
We use Wingate in all our Locations and it work fine but in some cases we get strange errors.
Some Pages did not work correctly that means for example if i try to login @flickr Page the redirect to the Login Page did not work.
The most other https-pages work fine, f.e. amazon, ebay.
If i change the configured proxy-server (other product - not WinGate) the login page works fine.
some facts:
- WinGate connect via upstream proxy to the internet
- Install a new "out of the Box" installation (Version 7.3.1.3535)
- for test - only configure the upstream proxy
In the Activity-Tab i can see the CONNECT
but the Page did not load...
i got ... "the connection was interrupted"
In the *global.log (with Debug-Level) i only see that..
11 20.06.2013 12:05:20.932 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 3 Request: http://www.flickr.com/signin
12 20.06.2013 12:05:20.948 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 0 sending request to up-stream server
13 20.06.2013 12:05:21.214 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 0 Received status 302 response from server
14 20.06.2013 12:05:21.214 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 0 Sending status 302 to client
16 20.06.2013 12:05:21.214 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 2 Traffic: 1278 983 977 1278 4s
17 20.06.2013 12:05:21.214 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 0 Server closed connection
18 20.06.2013 12:05:21.245 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 1 New connection:
19 20.06.2013 12:05:21.245 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 3 Request: CONNECT login.yahoo.com:443
20 20.06.2013 12:05:21.323 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 0 Server closed connection
22 20.06.2013 12:05:21.323 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 2 Traffic: 0 305 299 0 0s
23 20.06.2013 12:05:21.323 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 2 Traffic: 0 0 0 0 0s
24 20.06.2013 12:05:21.323 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 10 Session terminated: tunnel closed
25 20.06.2013 12:06:21.442 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 0 Client closed connection
26 20.06.2013 12:06:21.442 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 2 Traffic: 0 0 0 0 60s
27 20.06.2013 12:06:21.442 10.20.13.92 Unknown WWW Proxy Server 3312 4 debug 10 Session terminated: client disconnected
So the Client recieved the Status 302 and redirect to login.yahoo.com:443, but nothing happend..
In the sample Policy "SSL connect handler" the https-Request with Port 443 are Allowed at the end - if i switch "RestrictSSLPorts to "false" under "Data" ... the same - login page did not load :(
Some idea ? :(
Re: WinGate 7 some https-Redirects dont work..
Jun 21 13 3:05 am
Hi
I note you say WinGate connects via an upstream proxy.
the logs show the server (or upstream proxy) is disconnecting the tunnel through to login.yahoo.com
is there a policy on this upstream proxy that is blocking this?
If not, you may need to packet capture between WinGate and this upstream proxy to determine why it is being closed.
Regards
Adrien
I note you say WinGate connects via an upstream proxy.
the logs show the server (or upstream proxy) is disconnecting the tunnel through to login.yahoo.com
is there a policy on this upstream proxy that is blocking this?
If not, you may need to packet capture between WinGate and this upstream proxy to determine why it is being closed.
Regards
Adrien
Re: WinGate 7 some https-Redirects dont work..
Jun 21 13 11:27 pm
In this case - the "Server" are the upstream Server and not the Wingate-Server ?
The upstream proxy is our old software that we have to replace - This Server also has an Upstream-Server configured.
WinGate > Old Proxy > UpStreamServer (for test only, because I can’t use the needed IP from the Old Proxy )
If i connect directly to the Old Proxy (with my Browser) the Login works fine...
It does not matter wether WinGate use the Old proxy or the UpStreamServer, in both cases the login did not work.
Our normal configuration would be..
WinGate > UpStreamServer
In the logfile, the same @this configuration
Next week I'll try without upstream server..and maybe capture the traffic between WinGate & UpStreamServer ?
20 20.06.2013 12:05:21.323 10.20.13.92 Unknown WWW Proxy Server 2132 5 debug 0 Server closed connection
The upstream proxy is our old software that we have to replace - This Server also has an Upstream-Server configured.
WinGate > Old Proxy > UpStreamServer (for test only, because I can’t use the needed IP from the Old Proxy )
If i connect directly to the Old Proxy (with my Browser) the Login works fine...
It does not matter wether WinGate use the Old proxy or the UpStreamServer, in both cases the login did not work.
Our normal configuration would be..
WinGate > UpStreamServer
In the logfile, the same @this configuration
7:28.532 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 432 510317 debug 0 Received status 302 response from server
5335350 21.06.2013 11:57:28.532 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 432 510317 debug 0 Sending status 302 to client
5335352 21.06.2013 11:57:28.532 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 432 510317 debug 2 Traffic: 1168 1883 1100 1168 0s
5335353 21.06.2013 11:57:28.564 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 1 New connection:
5335354 21.06.2013 11:57:28.564 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 3 Request: CONNECT login.yahoo.com:443
5335355 21.06.2013 11:57:28.626 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 0 Server closed connection
5335357 21.06.2013 11:57:28.626 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 2 Traffic: 0 305 299 0 0s
5335358 21.06.2013 11:57:28.626 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 2 Traffic: 0 0 0 0 0s
5335359 21.06.2013 11:57:28.626 10.20.13.92 XXXXXXXXXXXXXXXXX WWW Proxy Server 3256 510321 debug 10 Session terminated: tunnel closed
Next week I'll try without upstream server..and maybe capture the traffic between WinGate & UpStreamServer ?
Re: WinGate 7 some https-Redirects dont work..
Jun 22 13 8:52 am
Hi
yes, I would recommend capturing the traffic between the 2 proxies. WinGate may be making slightly different requests than your browser would make, and for upstream proxy connections only supports Basic authentication whereas your browser would support other methods.
Regards
Adrien
yes, I would recommend capturing the traffic between the 2 proxies. WinGate may be making slightly different requests than your browser would make, and for upstream proxy connections only supports Basic authentication whereas your browser would support other methods.
Regards
Adrien