Package: wget
Version: 1.13.4-3
Severity: normal
Tags: upstream
* What led up to the situation?
i built a simple webserver with pythons BaseHTTPServer, which
requires a basic http auth. the server answers in http 1.0 and
sends no Connection: keep-alive header.
Now i tried to test it with wget, which sent at first (even though
i gave it user and password) no auth-string, probably to test which
auth-scheme is used.
the server sent a 401 with the WWW-Authenticate: Basic header, and NOW
wget tried to reuse the connection, which is already closed, and
should not have been reused, because there was no Content-length
header, there was no Keep-alive header AND it was http 1.0, but it
did, and the request failed. even though the server didn't do
anything wrong.
* What outcome did you expect instead?
i expected one connection per request which would have worked. i
didn't expect to read 'reusing existing connection' if there was
known to be no keep-alive
-- System Information:
Debian Release: 7.0
APT prefers testing
APT policy: (500, 'testing'), (500, 'stable')
Architecture: i386 (i686)
Kernel: Linux 3.2.0-4-686-pae (SMP w/2 CPU cores)
Locale: LANG=C, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/bash
Versions of packages wget depends on:
ii dpkg 1.16.9
ii install-info 4.13a.dfsg.1-10
ii libc6 2.13-37
ii libgcrypt11 1.5.0-3
ii libgnutls26 2.12.20-4
ii libgpg-error0 1.10-3.1
ii libidn11 1.25-2
ii zlib1g 1:1.2.7.dfsg-13
wget recommends no packages.
wget suggests no packages.
-- no debconf information
--
To UNSUBSCRIBE, email to
debian-bugs-...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact
listm...@lists.debian.org