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 connect() to daniel.haxx.se port 80 (#0)
* Trying 1.2.3.4... connected
* Connected to daniel.haxx.se (1.2.3.4) port 80 (#0)
GET / HTTP/1.1
Range: bytes=1-2
User-Agent: curl/7.18.2 (i486-pc-linux-gnu) libcurl/7.18.2 OpenSSL/0.9.8g
zlib/1.2.3.3 libidn/1.8 libssh2/0.18
Host: daniel.haxx.se
Accept: */*
--
/ daniel.haxx.se
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
