I know it's been a long time since I've posted here, but we've recently run into an error that we're having a difficult time tracking down.

We're using the following: Web Connection - 4.35, VFP 9.0, Windows Server 2008 R2 Standard.

This issue is for the most recent version of Chrome, Microsoft Edge does NOT have this problem.

After a successful login, any click immediately goes to the failed login page. I'm guessing that the session vars aren't being preserved.

Not much info to go on based on this...

If it's a server related problem you'd see it with any browser. If it works in Edge something is happening on the client end that's different.

Break out an HTTP proxy like Fiddler and compare what goes over the wire on both requests and compare.

On the server side - clear and pack the Session file just to make sure you don't have a corrupt session index - that could be a cause as look ups may be wrong. It could be that the session file got too large (over the 2 gig limit for example) which will make sessions go very wonky.

+++ Rick ---

I'm not really familiar with Fiddler. Is this something that would be installed on the web server? Are there some vids that show how to setup and track requests?

So just "fiddling" and I noticed a difference in the body. The size of the body when the request comes from Chrome is -1, which would explain why we're missing the session data.

No - you install it on your local machine. Then you run Fiddler which hooks up as a proxy in WIndows. Then you run the requests that you want to check out and examine the content for what works and what doesn't and compare.

This likely will give you an idea what's going on.

+++ Rick ---