Web page authentication & javascripts

[Ekkas]

Installed Wingate6.0.3 for a client with a very slow permanent connection (28k) and I sold it to them with the idea that caching will speed up everything. Now there is 2 problems:

1) On opening an extranet page that need authentication, the usern/passw box does not pop up and says 'unauthorized' something. I have to click Refresh or Ctrl-Refresh to get it.

2) On another web-page, with proxy (in OE) or with TR on, certain Javascript commands just doesn't work. When you point to the button, you can see the javascript command in the status bar, but clicking it just does nothing.

Now they're using Wingate but without caching which is kind of pointless for them.

Please give some advice
Thanks
Ekkas

[adrien]

Hi

If an Internet page requires authentication, this should not be cached by WinGate anyway, so it shouldn't be a matter of clearing the WinGate cache to get the proper login page - or is this a javascript-based login page?

If so, we now recommend setting the cache setting "number of days before rechecking HTML pages" to zero. Any other value overrides the cache freshness settings from the server - this was quite useful on slow links, but it did have the disadvantage of altering "freshness" of sites that change regularly.

As for Javascript commands not working - can you give an example? We don't touch the HTML/javascript content, so if it is not working, that would imply either a problem with the browser, or the site.

Are the clients configured to connect to the proxy, or are they being intercepted? Internet Explorer makes some weird decisions if it thinks it is talking to a proxy (like refusing to do NTLM auth, refusing to do certain other things).

Adrien

[Ekkas]

Whenever I
1)enable TR in Wingate
or
2) setup client IE to use proxy,

then I have this problem. Normal, slow connection without any caching has no problems.

Ekkas