I just tried the sequence in message #15 on curl 7.97.7 as well as the just-
released 7.21.4, and both those versions operated correctly:
$ curl -v --head -r 500-555
http://ftp.at.debian.org/debian/pool/main/g/glibc/glibc_2.7.orig.tar.gz | wc -c
* About to connect() to ftp.at.debian.org port 80 (
#include
* Daniel Stenberg [Sun, Jun 22 2008, 10:26:17PM]:
>> Maybe, and?
>
> And? And I am the main author of those parts of the code and thus the
> mistake is mine and I just told you about the background.
Well, no offense was intended; it just sounded a little bit weird.
>> GET and HEAD req
On Sun, 22 Jun 2008, Eduard Bloch wrote:
The code currently switches to Content-Range when another request than
GET is used, as then the resume is believed to be for content that is
sent. This is actually the first time I see somehow send range with HEAD
(and care about the header).
Maybe, and
#include
* Daniel Stenberg [Sun, Jun 22 2008, 08:57:44PM]:
> On Sun, 22 Jun 2008, Eduard Bloch wrote:
>
>>> No need for wireshark, curl can show its own headers. And they disagree
>>> with your report:
>>
>> Indeed. But now, please also add --head parameter and you will see...
>
> Indeed that look
On Sun, 22 Jun 2008, Eduard Bloch wrote:
No need for wireshark, curl can show its own headers. And they disagree
with your report:
Indeed. But now, please also add --head parameter and you will see...
Indeed that looks a bit strange, but then I think using a range in a HEAD
request is a bit
#include
* Daniel Stenberg [Sun, Jun 22 2008, 08:41:23PM]:
> On Sun, 22 Jun 2008, Eduard Bloch wrote:
>
>> this is an upstream issue: specify a custom range with "-r 1-2" or so
>> and watch the generated header with Wireshark.
>
> No need for wireshark, curl can show its own headers. And they dis
On Sun, 22 Jun 2008, Eduard Bloch wrote:
this is an upstream issue: specify a custom range with "-r 1-2" or so and
watch the generated header with Wireshark.
No need for wireshark, curl can show its own headers. And they disagree with
your report:
$ curl -v -r 1-2 daniel.haxx.se
* About to
Package: curl
Version: 7.18.2-1
Severity: normal
Tags: upstream
Hello,
this is an upstream issue: specify a custom range with "-r 1-2" or so
and watch the generated header with Wireshark.
Result: Content-Range: bytes 1-2/-1
Expected result: Range: bytes=1-2
Bad name and bad format are used ther
8 matches
Mail list logo
