cURL / Mailing Lists / curl-users / Single Mail


RE: Problem with --continue-at

From: Roth, Kevin P. <>
Date: Wed, 21 May 2003 12:43:07 -0400

Turns out the "file" I was trying to download was actually returning a Location: header..... Not sure if that caused any of the problem I was seeing. For what it's worth, my test URL was: "". I was testing with version 7.10.4 for Win32.

Regarding #1, I had -i and -D- in the same command line. I just now realized that this combination is *supposed* to give me two copies of the headers...

Regarding #3, THANK YOU! I really appreciate having this change; I'm surprised I didn't notice it in the changelog.

I have just one additional comment. I saw the following error when requesting the URL above in the manner described (curl -C- -O <URL>).

 curl: (33) HTTP server doesn't seem to support byte ranges. Cannot resume.

If I add a -L to the mix, it works fine.

Is there any chance some kind of warning could be printed, if curl sees a "Location:" header, but the -L wasn't specified? At least, if verbose output (-v) was requested?

- Kevin

-----Original Message-----
From: Daniel Stenberg []
Sent: Wednesday, May 21, 2003 12:06 PM

On Wed, 21 May 2003, Roth, Kevin P. wrote:
> 1. I was hoping adding "-D-" would help, and it does, to some extent. It
> does indeed show the response headers, but it ALSO appears to be adding
> them to the output file (my binary file).

Are you really sure? If so, it sounds like a bug, but a quick test in my end
did not show this behavior. It wasn't just that you already had used -i and
ruined the output file?

> 3. To fix it "properly", I'd propose that the HTTP response headers should
> NOT be written to the output file... At least, not in the case where
> -v was used, because the natural inclination would be that response
> headers would show up in the same place as request headers.

Starting with 7.10.5, the response headers are shown when -v is used, sent to
the same output stream that the rest of the -v output is. It especially makes
sense when you use ftp.

But, I'm not so sure this is a real problem anymore since -v will now give
you info you want so that you won't accidentally use -i unless you really
want the headers sent to the data output target.

This email is sponsored by: ObjectStore.
If flattening out C++ or Java code to make your application fit in a
relational database is painful, don't do it! Check out ObjectStore.
Now part of Progress Software.
Received on 2003-05-21