locked
WINHTTP future RRS feed

All replies

  • Hello Pseudonym_Karthik,

    With a few exceptions, WinINet is a superset of WinHTTP. When selecting between the two, you should use WinINet, unless you plan to run within a service or service-like process that requires impersonation and session isolation.

    Refer to WinINet vs. WinHTTP for Comparison of features between the two technologies. It will help you make a choice.

    If you choose WinHTTP, use the latest version of the technology, version 5.1. Version 5.0 is no longer supported.

    Do you use Windows 7 or Windows 10 or others?

    Best regards,

    Rita


    MSDN Community Support
    Please remember to click "Mark as Answer" the responses that resolved your issue, and to click "Unmark as Answer" if not. This can be beneficial to other community members reading this thread. If you have any compliments or complaints to MSDN Support, feel free to contact MSDNFSF@microsoft.com.

    Thursday, March 12, 2020 1:58 AM
  • deprecated WinInet

    Why do you say WinInet is deprecated? What says that?



    Sam Hobbs
    SimpleSamples.Info

    Saturday, March 14, 2020 9:45 PM
  • We are trying to implement a windows service that would also cater to HTTPS requests (acting as client and sometimes server). WinHTTP seems to be a good choice for the same. But we are not sure about its future.. We do have the choice of .NET but we have most of our application base in C++(STD + 

    From MSDN : Windows Internet

    WinINet does not support server implementations. In addition, it should not be used from a service. For server implementations or services use Microsoft Windows HTTP Services (WinHTTP).


    Sunday, March 15, 2020 9:56 AM