#include <hallo.h>
* 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 looks a bit strange, but then I think using a range in a HEAD
> request is a bit weird. ;-)
>
> 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? GET and HEAD requests should not be different except of the
method keyword... I see simply no point in using Content-Range in
any _request_, it's not defined for it.
> Do you actually expect something useful from this request or did you just
> notice this problem by looking at the headers?
Depends on the definition of "usefull". I am not going to use it in any
real-world application, I just needed a tool to quickly debug my
apt-cacher-ng daemon. So yes, it was used to retrieve real information
(check whether 200, 206 or 416 is returned) and it failed.
Regards,
Eduard.
--
<ij> Madkiss: Niemand kann so die Nachrichten mehr aufbereiten, dass
Otto-Normal-Bürger die versteht, da dieser viel zu dämlich dafür ist.
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
