Okay,

  Here is the output from trace-asci (took me a few moments to hunt down the
correct option). Hope this isn't too much data. I've tried to delete all
the sensitive portions and replace with ?, so some of the lengths may be
off. I'm afraid you're going to say what I've received is bad, but since I
have no control over the server, I'm very limited in what I can do about
that. Again thanks for all your help, thus far. (btw, when I said picky
earlier, I didn't mean to imply a perjorative, I was only hinting at that
lynx did seem to handle the chunky response from the command line, but curl
is much more rigorous in reporting errors than lynx -- which is a feature I
usually appreciate).

Brad

== Info: About to connect() to ??:???
== Info: Connected to ??? (???) port ???
=> Send header, 741 bytes (0x2e5)
0000: POST / HTTP/1.1
0011: User-Agent: curl/7.9.8 (i686-pc-linux-gnu) libcurl 7.9.8 (OpenSS
0051: L 0.9.6b)
005c: Host: ???
0078: Pragma: no-cache
008a: Accept: image/gif, image/x-xbitmap, image/jpeg, image/pjpeg, */*
00cc: Content-Length: 465
00e1: Content-Type: application/x-www-form-urlencoded
0112:
0114: <?xml version="1.0" encoding="UTF-8" ?>.<eoapi:Request xmlns:eoa
0154: pi="http://www.adp.com/eoapi" version="1.0"..ShowUnknownElementE
0194: rrors="Yes">..<Session>...<Connection>....<Product>???</Pro
01d4: duct>....<Server>???</Server>....<Password>???</Pas
0214: sword>....<Pooling>No</Pooling>...</Connection>...<GetSet>....<O
0254: bject>Inventory</Object>....<Group>??</Group>....<Selection>.
0294: ....WITH SOLD-DATE EQ ""....</Selection>...</GetSet>..</Session>
02d4: .</eoapi:Request>
<= Recv header, 17 bytes (0x11)
0000: HTTP/1.0 200 OK
<= Recv header, 28 bytes (0x1c)
0000: Transfer-Encoding: chunked
<= Recv header, 20 bytes (0x14)
0000: Content-Type: text
<= Recv data, 1438 bytes (0x59e)
0000: <?xml version="1.0" encoding="UTF-8"?><eoapi:reply xmlns:eoapi="
0040: http://www.adp.com/eoapi" version="1.0"><Session><Reply type="Co
0080: nnection"><ErrorMessage/><ErrorCode>0</ErrorCode></Reply><Reply
00c0: group="SALES" object="Inventory" type="GetSet"><Inventory><HostI
0100: temID>T05268</HostItemID><StockNo>T05268</StockNo><Balance>24226
0140: .00</Balance><DateSold/><NewUsed>NEW</NewUsed><Price>28030.00</P
0180: rice><Options>RE RH AY PG GH CR C7 TDA GAS DISC</Options><Make>T
01c0: OYO</Make><Account>23710</Account><Field23/><Field24/><Field25>1
0200: 28.25</Field25><Field26/><Field27/><Field28/><Field29/><Model>4R
0240: UN</Model><Field30/><Status>S</Status><ModelType/><IntColor>FV16
0280: </IntColor><Miles/><BodyType/><Engine/><ModelNo>8657</ModelNo><C
02c0: olor>1C0/SIL</Color><Year>00</Year><VIN>JT3HM84R7Y0037691</VIN><
0300: /Inventory><Inventory><HostItemID>T6003</HostItemID><StockNo>T60
0340: 03</StockNo><Balance>20068.88</Balance><DateSold/><NewUsed>USED<
0380: /NewUsed><Price>22243.00</Price><Options>PGE DGB EEB RAZ YDH 2DK
03c0: 24K 3VQ</Options><Make>CHRY</Make><Account>23100</Account><Fiel
0400: d23>35</Field23><Field24>6</Field24><Field25/><Field26/><Field27
0440: /><Field28/><Field29/><Model>SEBR</Model><Field30/><Status>S</St
0480: atus><ModelType>C</ModelType><IntColor/><Miles/><BodyType>CP</Bo
04c0: dyType><Engine>EEB</Engine><ModelNo>FJCP22</ModelNo><Color>PGE</
0500: Color><Year>96</Year><VIN>4C3AU52N0TE278423</VIN></Inventory><In
0540: ventory><HostItemID>T80489</HostItemID><StockNo>T80489</StockNo>
0580: <Balance/><DateSold/><NewUsed>
== Info: Closing connection #0

> -----Original Message-----
> From: curl-users-admin_at_lists.sourceforge.net
> [mailto:curl-users-admin_at_lists.sourceforge.net]On Behalf Of Brad
> Settlemyer
> Sent: Tuesday, January 21, 2003 12:32 PM
> To: curl-users_at_lists.sourceforge.net
> Subject: RE: Error about chunky parser
>
>
> >
> > > Thanks for the response, here is my new error message:
> > > curl: (56) Received problem 2 in the chunky parser
> >
> > Ah, the CHUNKE_ILLEGAL_HEX error code.
> >
> > libcurl didn't find a (single) hexadecimal digit where there was
> > supposed to
> > be (at least) one in the chunked stream.
> >
> > This indicates that the stream was malformated, not just ending
> > prematurely.
> >
>
> Great, given that the server I am talking to does not send the terminating
> character, how do I use curl with this server. I am actually
> interested in
> using lib curl rather than the command line tool, so any solution there
> would help as well. I tried changing the code to ignore the illegal hex
> error, and I received a response size error (off by 14 bytes), which I
> already ignore in some of my code. Since I don't have much knowledge on
> chunky responses, I'm unsure if ignoring the error is a safe way
> to resolve
> the problem, I'm afraid that it may not be.
>
> Thanks for your assistance thus far, and any additional
> suggestions you can
> provide,
> Brad
>
>
>
> -------------------------------------------------------
> This SF.net email is sponsored by: Scholarships for Techies!
> Can't afford IT training? All 2003 ictp students receive scholarships.
> Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
> www.ictp.com/training/sourceforge.asp
>

-------------------------------------------------------
This SF.net email is sponsored by: Scholarships for Techies!
Can't afford IT training? All 2003 ictp students receive scholarships.
Get hands-on training in Microsoft, Cisco, Sun, Linux/UNIX, and more.
www.ictp.com/training/sourceforge.asp
Received on 2003-01-21