Package: w3m Version: 0.5.3-5 Severity: normal -----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
This bug has existed - known to the developers - for 7 years now in lynx: http://lists.nongnu.org/archive/html/lynx-dev/2005-11/msg00012.html It also affects w3m. w3m advertises in its Accept-Encoding header sent to HTTP servers that it accepts the "compress" Content-Encoding. Upon receiving actual content with Content-Encoding: compress, it thoughtlessly passes it to gunzip, which obviously cannot handle compress (.Z) data and gives up saying it cannot decompress the stream. - -- System Information: Debian Release: wheezy/sid APT prefers testing APT policy: (500, 'testing') Architecture: amd64 (x86_64) Kernel: Linux 3.2.0-2-amd64 (SMP w/2 CPU cores) Locale: LANG=de_DE.UTF-8, LC_CTYPE=de_DE.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages w3m depends on: ii libbsd0 0.3.0-2 ii libc6 2.13-32 ii libgc1c2 1:7.1-8 ii libgpm2 1.20.4-4 ii libssl1.0.0 1.0.1b-1 ii libtinfo5 5.9-6 ii zlib1g 1:1.2.6.dfsg-2 Versions of packages w3m recommends: ii ca-certificates 20120212 Versions of packages w3m suggests: pn man-db 2.6.1-2 pn menu 2.1.46 pn migemo <none> pn mime-support 3.52-1 pn w3m-el <none> pn w3m-img <none> - -- no debconf information -----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.12 (GNU/Linux) iQHOBAEBAgA4BQJPtpxEMRpodHRwczovL3d3dy5kb21pbmlrLWdlb3JnZS5kZS9n cGctcG9saWN5LnR4dC5hc2MACgkQ2w6kvOIQdBKpcgv/QdXzazX36GMwNrPHgaZq RnvIrJhNddytdTDOw0gQpuCOOPwLqEPAM+nr4Jn2JMUg4yMR6Zc5WJG+pwzQ2m4Y M+NoPSLmBs4IEzCD3Hmp77oSO3CRba7djw4HBOEh18vjNDqjdFPWDJb4oIbpIt/Y 5JKb/asFfKXE2gTTfNwsqTa5OViI1PvkBi8NqKpOHVHt6fWtYDdPFMymn6veTlvR SnIKhFqoX+gKdOvkuxn5BZLQL8WZRIIDDPAtXCtgwTQe0pSHDCFC0C0QSZxQKOTe 43ZUfYpn8Rq2PP6bTtE142xQyvUDWTzxMaPZ3sWec9D1jxSGtEql0/4egOs6TYkK Ux4EBq/1GM9u4iCxnEIQQeIH9jKw+Lrd9os0Hyh9pSNeVV4Kr95wkiQrv6OG7O7Q T0NE8oq9gcF/k4TH2IgdiBAglQu0eoe3zVaSbl1lwjN9z9TxcnDwZnylY8M59lzB HwimipK3RmDoOxKGXXrpGL3fUAdVuoGZgSc4nYToh8bC =4u2k -----END PGP SIGNATURE----- -- To UNSUBSCRIBE, email to [email protected] with a subject of "unsubscribe". Trouble? Contact [email protected]
