by adrien » Nov 14 18 11:19 am
Hi
authentication in http is a challenge based system. the client makes a request, the proxy challenges it (407 response) which also advertises the supported methods, the browser makes the request again with credentials. This can involve prompting the user for user/pass or just automatically using existing credentials (such as the current logged in Windows user) if the proxy advertises support for NTLM or Negotiate.
So IE and chrome don't have a place to put proxy credentials (unlike Firefox).
The next thing to keep in mind is that by default WinGate does not challenge for authentication. It won't do this unless policy requires it. This means:
1. web access rules:
* require knowledge of the user (i.e. not Everybody); or
* explicitly use a re-authenticate rule (don't usually need this, and it can be trouble if you set it up wrong).
It's normal to want some sites to be accessible without authentication, while others may be accessible to only certain users or groups.
Regards
Adrien