From: Dean M. B. <mik...@gm...> - 2008-09-08 05:25:16
|
Hi Divye, On Sun, Sep 7, 2008 at 2:37 AM, Divye Kapoor <div...@gm...> wrote: > Hi Dean, > > On Fri, Aug 22, 2008 at 12:43 PM, Dean Michael Berris > <mik...@gm...> wrote: >> >> Right, but I'm more interested in something that can be made part of >> the unit tests so that I can verify whether the http::client we have >> has really sets the User-Agent header. > > I've committed a change (changeset 85) that allows you to see the HTTP > headers in the response from cgi-bin/requestinfo.py > There are a couple of bugs in the library that put in non-existent headers > in the response. However, it should be sufficient to test for setting of > http headers. > When you say "there are a couple of bugs in the library", which library are you referring to? And what exactly is the bug? > I'm thinking of refactoring the entire file to make parsing of the response > easy. > What would be the ideal response from the CGI script? CSV, XML or something > else? > Currently, the response is rather kludgy to parse. > Tab/space separated values work -- they can easily be parsed through std::ostringstream's -- as well as doing a '\n' delimited lines for pseudo-CSV. > Comments would be helpful. HTH (BTW, I'll take a look at your code to see if anything breaks in cpp-netlib) -- Dean Michael C. Berris Software Engineer, Friendster, Inc. |