"Brian Cassidy" <[EMAIL PROTECTED]> writes: > So, are there any proposed work-arounds, or is this completely useless now?
The decompresser just needs to be smarter about when to kick in. For a GUI browser it would kick in if you decide to display the document. This can be determined after looking at the content-type, but I'm sure they do all kinds of stuff to try to second guess the server (like looking at the URL suffix and peeking at the first block of the document content). For WWW::Mechanize you could for instance try to automatically undo content-encoding once code actually try to to match against content, parse forms etc. Regards, Gisle
