Hoping somebody can give some pointers as to why a 7K byte submission times out without reaching the server IIS on the office network, but a 1K post is almost instant.

Both worked fine as recently as March 2020.

Details:

WWVersion 6.21 sender app using wwHTTP.HTTPGET() to send mulitipart form ASCII data. nHttpPostMode=2, nHTTPConnectType=1. Verb=Post, HTTPS. Sending machine is a modern I7 Win10 machine.

Submissions (actually requests) with content of a few hundred bytes continue to show up in the server IIS log and are processed in < 1 second. However, sends of approx 7K bytes that used to be almost as quick are now yielding 12002: The operation timed out.

Receiving server: web.config has maxRequestLength="51200", maxAllowedContentLength="52428800". When the submission times out, it does not appear at all in the server IIS log, suggesting it's not actually reaching the server at all but is being stalled locally.

Stepping through wwHTTP.HTTPGetEx confirms the timeout is happening in HTTPSendRequest.

Firewall: Norton360 Deluxe, logs confirm outbound access is granted to the sending app with no logged blocks. Ditto server (which is actually a Windows 10 test machine)

Has anybody else experienced anything similar and/or any tips on what to log or check? Is there any way to log HTTPSendRequest locally?

/EDIT/ - FOUND IT:

On receiving machine, Event Viewer Windows\Application log shows Event code 3001, the Application Pool is timing out. Will DuckDuckGo further and update this post in case it's something new and exciting others may encounter(!)

Follow up: issue deep in the ASP stack somewhere. Eventually managed to track error at receiving end: OLE error code 0x80131530: Unknown COM status code in request.binaryread().

Only seen on Windows 10, same code works fine in Win7 and Win2013. Error eliminated by passing everything urlencoded and using request.form() with urldecode, rather than binaryread.

Sad to see weird new errors in something that had performed flawlessly for many years, but that's the excitement of IT I guess. Presumably something got "improved" deep in ASP or maybe people have stopped using binaryread these days...

What exactly are you doing? All very vague based on what you're posting here.

+++ Rick ---