HTTP Error 401.2
Apr 09 07 8:16 am
Hello All,
I am receiving an HTTP Error 401.2 when trying to access a site using WinGate. The error is pasted below:
You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.
I have set Wingate not to cache this site and still not able to view it.
When I browse to this page I get the above message; however when I delete my temp internet files and click refresh the page comes up.
Any guidance will be greatly appreciated.
Thank you
I am receiving an HTTP Error 401.2 when trying to access a site using WinGate. The error is pasted below:
You are not authorized to view this page
You do not have permission to view this directory or page using the credentials that you supplied because your Web browser is sending a WWW-Authenticate header field that the Web server is not configured to accept.
I have set Wingate not to cache this site and still not able to view it.
When I browse to this page I get the above message; however when I delete my temp internet files and click refresh the page comes up.
Any guidance will be greatly appreciated.
Thank you
Apr 11 07 8:56 am
Is your caching policy similar to the format below?
Apr 11 07 9:20 am
Yes Sir,
The caching policy is exactly like that.
The caching policy is exactly like that.
Apr 11 07 9:25 am
You might want to disable/purge WinGate's cache all together for the sake of testing. If you are still having problems can you post the login page URL here, or send it to me via jamesc -at- qbik -dot- com
HTTP Error 401.2
Jul 13 07 5:38 am
I am having the exact same problem with a site. I disabled caching and that seemed to work for my clients. Was there ever a fix for this issue so caching could be used?
Fritz
Fritz
Jul 13 07 8:31 pm
Also sent me an email to me with the URL:
So am I correct to assume that you:
a) Tried creating a caching policy for that web site - similar to the one in the forum post?
b) And the caching policy did not resolve your issue?
c) Only disabling all of WinGate's cache will allow connectivity?
I know that the WinGate cache has not had any maintenance done on it for some time. I also know that there are plans to revamp the caching system for WinGate 2007 but you will not get the benefit of that until it is released. The only way I can envisage finding a work around for you is by having a username and password that we can use to test that web site with; is that possible?
So am I correct to assume that you:
a) Tried creating a caching policy for that web site - similar to the one in the forum post?
b) And the caching policy did not resolve your issue?
c) Only disabling all of WinGate's cache will allow connectivity?
I know that the WinGate cache has not had any maintenance done on it for some time. I also know that there are plans to revamp the caching system for WinGate 2007 but you will not get the benefit of that until it is released. The only way I can envisage finding a work around for you is by having a username and password that we can use to test that web site with; is that possible?