WinHTTP error 12175 after days and huge number of requests

I use the Windows WinHTTP library to make http and https requests and sometimes get WinHTTP error 12175, usually after a few days of work (sometimes weeks), a hundred thousand to millions of requests.

If this happens, the only way to "fix" the error is to restart the service, and sometimes the errors will not go away until Windows (server) restarts.

Interestingly, this error appears "gradually": getting some of them for some HTTPS requests, then after a while the service receives them for 100% of https requests, and then they pop up even for normal HTTP requests (the service makes a lot of http requests and https, on the order of tens per second, for many servers). HTTP connections are made directly, without any proxies. OS - Windows 2012 R2.

AFAICT there is no memory leak or corruption, outside of 12175 errors, the rest of the service is working fine, has no access rights or suspicious exceptions, the service usually responds to requests, etc.

I have a suspicion that this could be due to Windows Update doing OS certificate updates, credential updates or something like that, but I could never confirm this.

Has anyone else observed this behavior? Any workarounds?

+3
windows https winhttp


source to share


No one has answered this question yet

Check out similar questions:

fourteen
hg serves as a Windows service
2
Apache 2.4.x + PHP 7 on Windows Server 2012 R2 does not release memory
1
WinHTTP Error URL Error
1
Restarting the web service
0
winhttp client and openssl server communication error
0
Failed to create view pg_stat_statements in Postgresql 9.4
0
Initialization sequence of an IIS web application repeatedly crashes and restarts
0
Windows MySQL service continues to run despite being told to stop
-1
WinHTTP Error 12029 Unable to Connect



All Articles
Loading...
X
Show
Funny
Dev
Pics