ie11 proxypass issue w/248
2 posts
• Page 1 of 1
ie11 proxypass issue w/248
This code works with FireFox and Chrome and other flavors of IE11. However, we have users where it is failing:
<VirtualHost www.mysite.com>
<Location /discoverer/>
ProxyMaxForwards 5
ProxyPreserveHost On
ProxyReceiveBufferSize 2048
ProxyTimeout 60
ProxyPass http://my.server.com:7778/discoverer/
ProxyPassReverse http://my.server.com:7778/discoverer/
ProxyPassReverseCookieDomain my.server.com www.mysite.com
RequestHeader unset Accept-Encoding
</Location>
</VirtualHost>
I am not sure if this is an IE11 issue or not. I had them load in safe mode and it still fails , they get a message saying unable to connect to http://my.server.com:7778/discoverer/ as if they completly ignore the proxy rule.
Any ideas?
<VirtualHost www.mysite.com>
<Location /discoverer/>
ProxyMaxForwards 5
ProxyPreserveHost On
ProxyReceiveBufferSize 2048
ProxyTimeout 60
ProxyPass http://my.server.com:7778/discoverer/
ProxyPassReverse http://my.server.com:7778/discoverer/
ProxyPassReverseCookieDomain my.server.com www.mysite.com
RequestHeader unset Accept-Encoding
</Location>
</VirtualHost>
I am not sure if this is an IE11 issue or not. I had them load in safe mode and it still fails , they get a message saying unable to connect to http://my.server.com:7778/discoverer/ as if they completly ignore the proxy rule.
Any ideas?
Re: ie11 proxypass issue w/248
Hello.
Where do they get this message from - Ape, IIS, IE, etc? I suppose they are getting this message from Ape?
There may be a permission issue if you have Windows authentication enabled in IE fro example. If users are authenticated IIS may impersonate them into their Windows accounts, which in turn may not have permissions to connect to remote server. Also there may be a network problem. Proxying is done server side and usually does not rely on browser or other clients properties, clients usually cannot even know their request is proxied. So there must be some reason other than browser version for this issue to happen.
Where do they get this message from - Ape, IIS, IE, etc? I suppose they are getting this message from Ape?
There may be a permission issue if you have Windows authentication enabled in IE fro example. If users are authenticated IIS may impersonate them into their Windows accounts, which in turn may not have permissions to connect to remote server. Also there may be a network problem. Proxying is done server side and usually does not rely on browser or other clients properties, clients usually cannot even know their request is proxied. So there must be some reason other than browser version for this issue to happen.
2 posts
• Page 1 of 1
Who is online
Users browsing this forum: No registered users and 32 guests