From: Ivan J. <ijo...@gm...> - 2010-06-05 17:11:51
|
On Fri, Jun 4, 2010 at 7:52 PM, Dean Michael Berris <mik...@gm...>wrote: > Hi Ivan, > > On Sat, Jun 5, 2010 at 12:51 AM, Ivan Johannessen > <ijo...@gm...> wrote: > > Hi Dean, > > I've just downloaded library and built the http_client.cpp sample. > > What version did you download? > > I downloaded the 0.6.1 tag and pulled in the changes from the 0.7 branch that allowed me to compile without SSL support. > > Testing > > it out by giving it the URL: http://www.google.com results in a "Missing > > Transfer Encoding" exception. Looking the code in > sync_connection_base.hpp I > > see that either a Content-Length or Transfer-Encoding header is required. > > However, the response fromwww.google.com does not contain a message > body(I > > assume because the Connection:close header was included in the request), > > thus the presence of either of those headers are optional. Thoughts? > > Actually I would say it's because the client in the HTTP example > doesn't follow directs automatically (IIRC). I need to check this. > > The 0.6.1 version has an HTTP client that is HTTP/1.1 compliant and > thus should support already HTTP/1.0 responses from servers. In the > HTTP/1.1 spec, the server's HTTP/1.1 response *should* contain either > a Transfer-Encoding header, or a Content-Length header. > > In the case of the example, I don't think it adds the > "follow_redirects" constructor option. I'll dig into it later but can > you check whether the response is an HTTP 200 or an HTTP 302? > > The http_client.cpp do follow redirects and the response is a HTTP/1.1 response with status 200. This issue is by no means a show stopper for me but I pointed it out because I believe it is in disagreement of the RFC: http://www.w3.org/Protocols/rfc2616/rfc2616.html I could not find anything in the RFC that stated that a response without a body "should" or "must" contain either headers. > Thanks and I hope this helps! > > -- > Dean Michael Berris > deanberris.com > > > ------------------------------------------------------------------------------ > ThinkGeek and WIRED's GeekDad team up for the Ultimate > GeekDad Father's Day Giveaway. ONE MASSIVE PRIZE to the > lucky parental unit. See the prize list and enter to win: > http://p.sf.net/sfu/thinkgeek-promo > _______________________________________________ > Cpp-netlib-devel mailing list > Cpp...@li... > https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel > |