I am debugging a SOAP webservice hosted by SQL Server 2008. I know that those are deprecated in future versions and we should consider a different technology, of course. There is an exposed procedure which legitimately runs for quite a long time sometimes, depending on circumstances. Now, when it spills over 120 seconds, the connection gets reset due to a timeout, in the http error log there is an entry
443 HTTP/1.1 POST /APIDevelop/ - - Timer_EntityBody -
and the CURL-based library on the clientside gets a 104 error (CONNRESET). We have tried to adjust the timeout settings for http.sys by running
netsh http add timeout timeouttype=idleconnectiontimeout value=480
but it seems that http.sys is not impressed by these settings (which end up in HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\services\HTTP\Parameters), not after restarting SQL Server and eventually the whole server, either. The timeout is still there at 120 seconds. Actually, the call takes around 130s but I attribute the difference (maybe, mistakenly) to other latencies.
Anyway, the question is: SQL Server is using http.sys for running its SOAP endpoints - how can I configure http.sys's in this case? Specifically for timeouts?