Re: w3m -> standard, lynx -> optional
On 22 Jan 2004 18:48:59 +0900, Miles Bader <miles@lsi.nec.co.jp>
wrote:
>The thing is, though, the [current version of] elinks in debian
>_doesn't_ seem do this -- I just tested it.
Try to reproduce it with the procedure described in #221207.
Looks like elinks behaves this way if the web swerver delivers the
document as Content-Encoding: x-gzip, Content-Type: text/plain what
ftp2.de.debian.org does for .diff.gz files.
Behavior of web swervers seems to be different. ftp2.de.d.o says
text/plain, ftp.de.d.o says application/x-gzip and ftp.d.o says
"text/plain; charset=iso-8859-1" which seems to be the normal behavior
for a straight apache install from Debian stable.
What would be correct swerver and client behavior for a .diff.gz file?
Greetings
Marc
--
-------------------------------------- !! No courtesy copies, please !! -----
Marc Haber | " Questions are the | Mailadresse im Header
Karlsruhe, Germany | Beginning of Wisdom " | Fon: *49 721 966 32 15
Nordisch by Nature | Lt. Worf, TNG "Rightful Heir" | Fax: *49 721 966 31 29
Reply to: