Skip to content

Commit 42c7d5b

Browse files
authored
Update README.md
1 parent 3904d6c commit 42c7d5b

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

README.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -260,7 +260,7 @@ Setting the `Timeout` option sets the maximum allowed time the connection or req
260260
```c++
261261
wrap::Timeout{1000,"connection"}
262262
```
263-
Since WNetWrap is built on top of WinINet, it’s important to know what setting this `Timeout` does to the request. It creates a worker thread which executes the connection or request call. This thread is then monitored and killed if it takes longer than the timeout specified. The reason this approach is taken is that the normal method of setting a timeout with WinINet does not work, due to a 20+ year old MS bug. You can find out more about this workaround [here](https://mskb.pkisolutions.com/kb/224318). What it means in practical terms is that `Timeout` cannot be set to a value high than WinINet's default (currently 1 hour).
263+
Since WNetWrap is built on top of WinINet, it’s important to know what setting this `Timeout` does to the request. It creates a worker thread which executes the connection or request call. This thread is then monitored and killed if it takes longer than the timeout specified. The reason this approach is taken is that the normal method of setting a timeout with WinINet does not work, due to a 20+ year old MS bug. You can find out more about this workaround [here](https://mskb.pkisolutions.com/kb/224318). What it means in practical terms is that `Timeout` cannot be set to a value higher than WinINet's default (currently 1 hour).
264264
265265
### Security Certificate Info
266266

0 commit comments

Comments
 (0)