I found the problem.

There were two distinct errors, the first was that the curl wrapper was
using a get and not a post , and the second was that the request was
getting truncated because it contained a #. The original developer had
overridden the encoding with their own home grown one that did not
handle the #'s. The second problem was difficult to find because I
assumed that the server was truncating the request because I had not
correctly fixed the post problem.

Many thanks for your patience and help!

-----Original Message-----
From: curl-library-bounces_at_cool.haxx.se
[mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of man_at_tfhs.net
Sent: Thursday, May 12, 2005 10:46 AM
To: libcurl development
Subject: RE: Request is getting truncated by my WAS App server

any chance there is some kind of proxy between you and the server,
perhaps a transparent one?

allan

On Thu, May 12, 2005, "Cobb, Richard" <Richard.Cobb_at_LibertyMutual.com>
said:

> I am sure now that it is performing a post because I see it coming
> into the app server as a post. However the XMLData parameter is
> coming into the post inside the header and NOT the body. Their must
> be a 2k limit on the header size of my server, because it truncates it

> down to 2k.
>
> -----Original Message-----
> From: curl-library-bounces_at_cool.haxx.se
> [mailto:curl-library-bounces_at_cool.haxx.se] On Behalf Of man_at_tfhs.net
> Sent: Thursday, May 12, 2005 9:48 AM
> To: libcurl development
> Subject: RE: Request is getting truncated by my WAS App server
>
>
> ok, what i should have said was that your original data sent was a
> GET, but the code you list below does a post. are you sure that this
> is the code that made the request, and not some other code? or perhaps

> there is something in your older version of libcurl that made this
> perform a get instead...
>
>>>> printf("%s",pTURL);
>>>> curl_easy_setopt(localcurlHndl, CURLOPT_URL,
>>>> "http://10.110.188.229:9080/curlGetPost/curlGetPost" );
>>>> curl_easy_setopt(localcurlHndl, CURLOPT_POSTFIELDS,pTURL);
>>>> curl_easy_setopt(localcurlHndl, CURLOPT_POSTFIELDSIZE,
>>>> strlen(pTURL));
>>>>
>>>> curl_easy_perform(localcurlHndl);
>
> can you get a tcpdump or ethereal dump of the communication with a
> working transaction from your browser and a non-working one from your
> curl app? i find comparing those (in ethereal) is most helpful.
>
> allan
>
>

--