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?
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.
GET and HEAD requests should not be different except of the method
keyword...
Of course, I don't deny that. I try to understand what you're trying to do
though.
I see simply no point in using Content-Range in any _request_, it's not
defined for it.
Wrong. But that's not what this bug report is about.
--
/ daniel.haxx.se
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
