Your message dated Wed, 16 Nov 2011 22:46:36 +0100
with message-id <[email protected]>
and subject line Closing
has caused the Debian Bug report #487567,
regarding curl: uses wrong header for custom Range request
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
487567: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=487567
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
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 there, see RFC 2616 §14.35 and §14.16
for details. Actually this looks like the response header rather then
Range: request header.
Regards,
Eduard.
-- System Information:
Debian Release: lenny/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)
Kernel: Linux 2.6.25.6 (PREEMPT)
Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages curl depends on:
ii libc6 2.7-11 GNU C Library: Shared libraries
ii libcurl3 7.18.1-1 Multi-protocol file transfer libra
ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime
curl recommends no packages.
-- no debconf information
--
<youam> au ja! kratz mich, beiss mich, sende mir TOFU!
--- End Message ---
--- Begin Message ---
Version: 7.21.4-1
The bug seems fixed. Closing it.
Cheers
--- End Message ---
