curl-users
Re: stdin problem in version 7.10.6
Date: Wed, 4 Feb 2004 18:21:23 -0500
It appears that the problem is that curl is ignoring the Content-Length
header and including a Transfer-Encoding: chunked. The extra characters
before and after the stdin in the log are the chuck sizes in hex. I can
eliminate the Transfer-Encoding header using an empty -H option, but can't
get curl not to chunk the output in 7.10.6.
Are there any options to disable chunking when using stdin and you know the
total number of characters and included a Content-Length header?
There is a bug reported fixed in 7.11.0 that seems like it may apply to this
situation.
Thanks,
-Len Krause
Excellware, Inc.
----- Original Message -----
From: "Len Krause" <len.krause_at_excellware.com>
To: <curl-users_at_lists.sourceforge.net>
Sent: Wednesday, February 04, 2004 5:05 PM
Subject: stdin problem in version 7.10.6
> I have an application that uses curl with stdin that works fine in curl
> versions 7.9.3 and 7.9.8 but fails in 7.10.6. All three versions work
fine
> when passing the file name instead of using stdin.
>
> The new --trace-ascii log show several extra characters before and after
> what is sent to stdin. The progress display of the number of characters
> sent is also higher than from stdin.
>
> Could there be some debug options enabled when using stdin that didn't get
> disabled?
>
> Thanks,
> -Len Krause
> Excellware, Inc.
>
>
>
>
>
>
>
>
> -------------------------------------------------------
> The SF.Net email is sponsored by EclipseCon 2004
> Premiere Conference on Open Tools Development and Integration
> See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
> http://www.eclipsecon.org/osdn
>
-------------------------------------------------------
The SF.Net email is sponsored by EclipseCon 2004
Premiere Conference on Open Tools Development and Integration
See the breadth of Eclipse activity. February 3-5 in Anaheim, CA.
http://www.eclipsecon.org/osdn
Received on 2004-02-05