Http Client Protocol Issues

If you use any of these solutions, Please let me know so I can track if any of this is useful to you! Thanks! This is an area to share observations I have made working with Http Client Protocols and the associated technologies. I currently work for the Microsoft team that supports the WinInet, WinHTTP and System.Net API's and classes associated with these technologies. This is not a replacement for Microsoft Support, but an area to discuss these technologies. These postings are provided "AS IS" with no warranties, and confer no rights. Use of included code samples are subject to the terms specified at Microsoft - Information on Terms of Use

Workaround For WinInet DNS not refreshing when using KB 263558

If you are making Synchronous calls in WinInet, the DNS timeouts don't appear to work when set (see: http://support.microsoft.com/kb/263558 ).

Async calls do however work correctly.

One workaround is to simply restart the application using WinInet. 

I found a code workaround for the issue as well.  Simply open and close the handle you get with the InternetOpen call then open it again:

hOpen= ::InternetOpen(.....);

InternetCloseHandle(hOpen);

hOpen= ::InternetOpen(.....);

// now use handle...

 The performance impact will be very low.

 -Jeff

Published Friday, November 14, 2008 9:45 AM by jpsanders
Filed under:

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

No Comments

Leave a Comment

(required) 
(optional)
(required) 

  
Enter Code Here: Required
Submit

© 2009 Microsoft Corporation. All rights reserved. Terms of Use  |  Trademarks  |  Privacy Statement
Microsoft
Page view tracker