Web Connection
Duplicate hits on new, fast server
Gravatar is a globally recognized avatar based on your email address. Duplicate hits on new, fast server
  Ken Green
  All
  Jul 1, 2020 @ 04:49pm

My client upgraded to a new, very fast, server. One consequence is that client requests to wc.dll sometimes double.

On his main server he has 4 Web Connections running: 2.96 circa 1998/99 (he didn't want to pay for changing his, by then extensive, code to 3.0's new requirements); wc.dll is dated 01/08/1999. Another station has a 5th Web Connection used only for specialty tasks.

Back to his server, he has two newer Web Connections running a later version (wwserver.prg's latest change: 7/27/04; wc.dll is renamed and on a different folder and dated 04/12/2004). This supplies all in-page web services.

The doubling occurs on all of the Web Connections. The 2nd instance is often run right after the first one. However, they have different .TMP file names. On the 5th Web Connection, the 2nd task dutifully waits for the 1st to finish.

Of course, we've double-checked that only a single request has been made (no dual button clicks). Further, this has only occurred once the new server came on line.

Any thoughts for a fix?

Update 7/02: In a subclassed CheckForCGIFile() method, I saved selected requests. Reviewing those, I see that the request filenames are DIFFERENT. Yet the requests are identical even down to portions contining randomly defined numbers.

Could this be an IIS problem?

Gravatar is a globally recognized avatar based on your email address. re: Duplicate hits on new, fast server
  Rick Strahl
  Ken Green
  Jul 1, 2020 @ 05:58pm

Duplicate hits mean, either there are - duplicate hits somehow generated by the browser... Or requests require autherntication which could result in double requests for the auth requests. If you're using Windows Authentication on the server, and are running an ancient IIS version requests can easily double up.

Other than that - not so much. If multiple requests hit the server they must be generated from somewhere. To be sure use an HTTP client (rather than a browser) and/or use an HTTP proxy like Fiddler to trace the requests and see what the second request is doing and where it exactly is generated (look at at the headers for request and response).

+++ Rick ---

© 1996-2020