Use this forum to post questions relating to WinGate, feature requests, technical or configuration problems
Post a reply

Wrong Search Results on different Webpages

Dec 14 04 8:56 pm

If I search for example for articles on the webpage www.ulmer.at : At the tope of the page I can change Artikel for a articlenumber for example 10900 or other articlenumber I cant receive the right results.
Without Wingate proxy it works, with MS ISA it works !!
This behavior I have with a lot different pages.
I run Wingate 6.0.3. and MS Internetexplorer.

Dec 15 04 8:07 am

Interesting. I'm going through WinGate as well and when I search for 10900 I get 9 results:

M06578, M06576, M11213, ... E10900, M10900, ... T23292

They all seem to (Looking at the descriptions and body text) contain some reference to that number.

How do you connect through WinGate? Are you using Proxy, WGIC or NAT?

Do you have caching enabled? (It's enabled here, but just thought I should check that). What about plugins?

Dec 16 04 7:44 am

I am using only the Proxy function, caching is enabled.
I found out that, when I search on this webpage the number f.e. the 10900 I will receive one time the right result. Then I search for a new number f.e. 10000 I still get the result from 10900. But when I press the button reload on the Internetexplorer I get the right result for 10000 ??
I tried this on different Servers with Wingate, I have always the same problem.
I use Kaspersky Plugin, but I also disabled the Plugin --> the same result.

Dec 16 04 7:45 am

That sounds like a caching problem. Try it with the cache disabled?

Dec 16 04 8:00 am

Thanks
I disabled caching for this page, and now it works.
Last edited by jbl on Dec 16 04 8:11 am, edited 1 time in total.

Dec 16 04 8:11 am

I can't duplicate that behavior. Going through WinGate with Caching enabled / disabled using IE or Firefox I always get the correct results. Doesn't matter if it's NAT + Intercept / Proxy direct.

Maybe a file is corrupt in your local WinGate cache that is causing this problem - or maybe your browser has cache corruption.

The easiest way to test that would be to clear the cache (On both sides).
Post a reply