Wanted: Developer feedback for our "Next Generation" client HTTP stack

As we begin the planning phase for our "Next Generation" client HTTP stack, we would love to hear from developers using our existing APIs (WinINet and WinHTTP). Please help us understand what your experience has been so far and what you would like to see in any future releases by filling out this survey.


 -Jonathan Silvera

Comments (5)

  1. Apologies if there’s a way of doing this already that I just haven’t figured out, but…   I need the ability to automatically use the current IE proxy settings when they’ve been set via automatic detection or a configuration URL.   The WinHTTP documentation seems to be pointing at proxycfg.exe, and proxycfg.exe punts on these cases.

  2. Clarifying previous response: I’m referrring to WinHTTP.  I’m calling the COM interface from a scripting environment.

  3. Prasad Thota says:


    Unfortunately, WinHTTP doesn’t have the capability to read IE’s proxy settings from COM scripting environments.

    COM components either specify the proxy directly, or rely on proxycfg (netsh in Vista) to set it for them.

    Currently, the only way to do this is using a Win32 API –  WinHttpGetIEProxyConfigForCurrentUser from a C/C++ app.

    Hope that helps.


  4. nick says:

    We would also like to hear from you what the most popular / most sensible / most creative requests/responses have been.

    Its the least you can do for us survey takers 😉

  5. Pablo Abraham says:

    Socks 4 and 5 will be apreciated.

Skip to main content