I'm looking for a C++ library that implements or enables the implementation of a HTTP client. It should handle cookies as well.
What would you propose?
Thank you in advance for your time.
views:
1143answers:
7
+8
A:
Curl++ is an option, particularly if you want things in more of a C++ style.
bdonlan
2009-05-04 23:21:09
broken link (15 chars)
Assaf Lavie
2009-12-26 04:08:19
+5
A:
C++ (STL) does not have a HTTP or network library by default, you will have to do with something else.
libcurl should do what you want. cURL++ is the same libcurl wrapped in a shiny C++ wrapper.
The Unknown
2009-05-04 23:21:45
+1
A:
If it's for windows, take a look at Windows HTTP Services (WinHTTP)
http://msdn.microsoft.com/en-us/library/aa384273(VS.85).aspx
Microsoft Windows HTTP Services (WinHTTP) provides developers with an HTTP client application programming interface (API) to send requests through the HTTP protocol to other HTTP servers.
WinHTTP offers both a C/C++ application programming interface (API) and a Component Object Model (COM) automation component suitable for use in Active Server Pages (ASP) based applications.
For Cookies http://msdn.microsoft.com/en-us/library/aa383261(VS.85).aspx
Thanks for your suggestion. It's plain C without any of C++ there. I'd really like to make use of Bjarne's hard work (http://research.att.com/~bs).It should be forbidden for a couple of years now to use C in application programming :)
Piotr Dobrogost
2009-05-05 07:45:37
+1
A:
You can try WinInet
http://msdn.microsoft.com/en-us/library/aa385331(VS.85).aspx
In contrast to WinHTTP, it's more client-side oriented.
Eugene
2009-05-05 05:44:38
Piotr Dobrogost
2009-05-05 07:55:34
You can also look at URL monikers:http://msdn.microsoft.com/en-us/library/ms774965(VS.85).aspx, it relies on WinInet(as I think), but provides COM like interface.
Eugene
2009-05-05 09:58:36
@Piotr: trust me, if you think WinHTTP is bad, you will absolutely *HATE* WinInet... It is an astonishingly unfriendly API, even if you're used to working with C libraries. And the worst part of it may be the WinInet constants and errors that "bleed through" to higher-level libraries such as MSXML... The big advantage of WinInet is that if a user has already configured proxy settings for their account (via the administrator options or the IE / Internet Options control panel) then WinInet will pick those up automatically; other libraries may need explicit configuration. Windows-only though...
Shog9
2010-01-27 19:05:21
+4
A:
Take a look at Poco Libraries.
I started using them as they are portable and it's a joy to work with. Simple and clean - though I haven't dived in anything fancy for the moment.
da_m_n
2009-07-31 12:13:25
Poco is a very nice library that in my opinion deserves more publicity than it seems to get
John Burton
2009-07-31 12:21:58