WWW Proxy server policy

[Ann]

Hi there,

Question for you.

I have a policy setup in the www proxy server.
The recipient is rights are restricted by request.
There is a filter setup that the HTTP URL contains
"specific" websites.

When the user goes to www.mapquest.com
a windows username and password box comes up
for as an example:

connecting to a514.aol.akamai.net

The user has to put in their username and password
for several of these boxes or keep clicking cancel.

Then the website finally comes up.

I added a filter for akamai.net and the boxes still come up.

The problem is that they have to do this every time
they go to www.mapquest.com.

How can we stop this from happenning?

Thanks!
Ann[/url]

[adrien]

Hi

I take it that this is using authentication in WinGate's web proxy, with transparent proxy / intercepted connections?

When a browser is configured to connect out through NAT, and you intercept connections and force authentication, then the browser won't try to use the same credentials it used for one site on another subsequent one. So each time it gets an authentication challenge for a new site, it pops up the login dialog. Some pages include images and parts off many different sites, so loading a single page can cause a browser to display many login dialogs.

there are 2 options to get around this.

1. Configure the browsers to use a proxy. When the browser knows it's talking to a proxy, then it knows that when the proxy challenges it for authentication, it is actually authenticating to the proxy, so can re-use the credentials.

2. Specify that the browser always log in automatically with the current credentials. This one only works for NTLM logins where you are using the Windows user database in WinGate.

Regards

Adrien

[Ann]

I chose the option to make it go through the browser.
That worked.

Now our access to secure sites (https) is not working?

How can I fix this?

Thanks,
Ann

[adrien]

Hi

For secure access through the proxy, you specify the same IP and port in the proxy configuration as you do for normal HTTP access.

Or you can leave it blank and use NAT for this (which is generally more reliable).

Which version of WinGate are you using? We had some problems with authenticated secure access through the WWW proxy in an earlier version - not exactly sure which one.

Adrien