Web page delivery just stops!

[bjones]

I have recently installed Wingate for a client and they have a problem accessing one particular site. During a form post (and subsquent redirection to response page) the page delivery stops and they get something like

<INPUT TYPE="HIDDEN" NAME="VF_

I have tried this with my installation and get the same problem.
All other web sites that I have tried through this setup work fine.

I seem to recall this sort of problem with 3.x some time ago.

I have looked at the logs, but all seems normal. I have tried accessing the web site using the same machine with a direct connection to the internet (i.e. not through Wingate) and the problem web site works every time.

Wingate 5.2.0

Any ideas?

Thanks
Bob

[labull]

Bob,

Do you have PureSight or KAV installed on this system? If so you might disable them and test.

Also, 5.2.2 is rock solid with several fixes - you could try upgrading.

Larry

[bjones]

Puresight or KAV not installed, although we both use ZoneAlarms.

I'll try 5.2.2.

B.

[labull]

Try disabling Zone alarm while you're at it.

[bjones]

Tried 5.2.2 and have removed Zone Alarm.

The web site now partly works in that 50% of the time, the requested page is delivered, the other 50% come up with same problem.

I have spoken with the web site developer and am told that the web site relies heavily on a session cookie, which presumably is passed through Wingate to the requesting browser.

Its really odd that it works only 50% of the time, since clearly the browser has received the session cookie to allow the 50% working. If I run a browser on the wingate machine (and therefore connects directly with the web site, it works 100% of the time)

I wondered if there is a timing issue between the browser request and the session cookie management within Wingate?

B.

[Pascal]

I have spoken with the web site developer and am told that the web site relies heavily on a session cookie, which presumably is passed through Wingate to the requesting browser.

The easiest way to debug this is to turn on full logging in the WWW Proxy Service. Run the sessions and note when one succeeds and when one fails. Preferably, copy and paste the relevant portions out when (a) it succeeds and (b) fails.

Then you can either post them here, so we can compare the two versions and see where the problem might be, OR email them directly to myself or one of the other Qbik people.