Paul Slootman <[EMAIL PROTECTED]> writes: > > From: Walter Hofmann <[EMAIL PROTECTED]>
> > I cannot access http://groups.yahoo.com/ via wwwoffle. > > > > The browser just displays an empty document. > > I tried with mozilla and lynx. > > It works just fine without wwwoffle. > > > > The following message is logged: > > Mar 30 23:41:46 bilbo wwwoffles[23091]: Error reading reply body from remote host >[zlib: unknown compression method]. > > Mar 30 23:41:54 bilbo wwwoffles[23097]: Error reading reply body from remote host >[zlib: unknown compression method]. > > Mar 30 23:42:02 bilbo wwwoffles[23099]: Error reading reply body from remote host >[zlib: unknown compression method]. > > Mar 30 23:42:04 bilbo wwwoffles[23101]: Error reading reply body from remote host >[zlib: unknown compression method]. > > Mar 30 23:42:08 bilbo wwwoffles[23103]: Error reading reply body from remote host >[zlib: unknown compression method]. > I see myself that with -d 9 I get: > > Mar 31 01:44:33 wurtel wwwoffles[2250]: URL='http://groups.yahoo.com/'. > Mar 31 01:44:33 wurtel wwwoffles[2250]: Directory 'http/groups.yahoo.com' does not >exist [No such file or directory]; creating one. > Mar 31 01:44:34 wurtel wwwoffles[2250]: Server has used 'Content-Encoding: >deflate'. > Mar 31 01:44:34 wurtel wwwoffles[2250]: Cache Access Status='New Page'. > Mar 31 01:44:34 wurtel wwwoffles[2250]: Error reading reply body from remote host >[zlib: unknown compression method]. > Mar 31 01:44:34 wurtel wwwoffled[2246]: Child wwwoffles exited with status 0 >(pid=2250). > - mozilla displays an empty page. I checked mozilla's own cache, and > there's a gzipped file with zero bytes there, so it looks like it > indeed doesn't get any data whatsoever. There is a bug in Mozilla. It can't handle deflate compression method even though it claims that it can. http://bugzilla.mozilla.org/show_bug.cgi?id=105292 > - In the wwwoffle cache directory http/groups.yahoo.com there's a file > with the wwwoffle error message for not being able to decompress the > data received. So why didn't mozilla get this... Don't know. > - Putting wwwoffle offline at this point and reloading in mozilla > displays the error message that was in the wwwoffle cache. So why > didn't wwwoffle feed that to mozilla when it was online? Perhaps the > compression confusion led to wwwoffle feeding the error message to > mozilla uncompressed but flagged as being uncompressed (or vice > versa)? Possible. > - Testing with lynx displays the real page just fine... I had expected > that the compression between wwwoffle and web server would be > independent of whether the client requested it or not?! It should be. > - Now putting wwwoffle offline and reloading in mozilla again shows only > a blank page, even though the log says "Cached Page Used", giving the > impression that mozilla should show the same as what lynx did. Mozilla can't handle deflate data. I imagine that what is happening (and this is a wild guess) that groups.yahoo.com is sending back different data depending on the User-Agent header that it gets. It knows that Mozilla can't handle deflate, so it sends what Mozilla can handle with an invalid header saying that it is deflate. This explains why WWWOFFLE cannot compress it unless you use Lynx where the proper deflate is used. This theory can be tested by using different User-Agent strings and then looking at the debug output of WWWOFFLE. We have discussed before on this list servers that cannot send correctly compressed data using the deflate method. It does seem problematic for some people. -- Andrew. ---------------------------------------------------------------------- Andrew M. Bishop [EMAIL PROTECTED] http://www.gedanken.demon.co.uk/ WWWOFFLE users page: http://www.gedanken.demon.co.uk/wwwoffle/version-2.7/user.html
