On Mon, Jan 06, 2003 at 10:25:07PM -0200, Fr?d?ric L. W. Meunier wrote:
The garbage is gzip'd data. Essentially what is happening is that
the remote site is sending an error message followed by the actual page
content which is gzip'd. We encountered a site which misbehaved last
year - for which I made a workaround (not adding lynx's base-url stuff
when dumping the page).
Why w3m works? A couple of possibilities to investigate:
a) it's not advertising that it can accept gzip'd data (not likely)
b) it is detecting the couple of magic bytes sent by gzip at the
beginning of the gzip'd stream and switching into ungzip mode
at that point.
But w3m 0.3 doesn't work either (just tried it).
I'll have to lookup the most recent code
and see if it's trying to do the latter.
--
Thomas E. Dickey <[EMAIL PROTECTED]>
http://invisible-island.net
ftp://invisible-island.net
; To UNSUBSCRIBE: Send "unsubscribe lynx-dev" to [EMAIL PROTECTED]
