On Tue, Jun 8, 2010 at 1:40 AM, Ivan Johannessen <[email protected]> wrote: > > > On Sun, Jun 6, 2010 at 7:01 AM, Dean Michael Berris <[email protected]> > wrote: >> >> That's odd, you don't get a body from the HTTP 200 OK response from >> www.google.com? >> > That is correct. >
Whan you say you don't get a body, that means cpp-netlib already throws right? I checked the RFC again and it seems I forgot to support the case where the server just streams the contents and closes the connection without specifying a transfer-encoding nor a content-length (as described by http://www.w3.org/Protocols/rfc2616/rfc2616-sec4.html#sec4.4) which is an oversight on my part. Please file an issue at http://github.com/mikhailberis/cpp-netlib/issues so I can track the fix for it. I don't think it would be hard to fix it but I would like to track work done against it so I can "focus". :) >> >> Conforming HTTP 1.1 servers should use an HTTP 204 No Content response >> instead if it doesn't intend to send a body. Although an HTTP 200 OK >> should have either a "Content-Length" or "Transfer-Encoding: chunked" >> last time I checked. >> >> I'll try to look deeper into this though, thanks for reporting. >> > Ah, looks like google is not doing the right thing. Thanks for a great lib. > I'll be using it in a cross platform(Windows/OSX/Linux) app soon. Cool, you might want to hold off until I fix the bug with the HTTP 1.1 client implementation. :) Have a great week ahead 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 [email protected] https://lists.sourceforge.net/lists/listinfo/cpp-netlib-devel
