Joachim Groh <[EMAIL PROTECTED]> wrote:
> since upgrading to Version 2.6c wwwoffle adds "Content-Encoding: x-gzip"
> to many (all?) html-pages. Unfortunately Netscape 4.77 refuses to show
> these pages. Wget and Konqueror (KDE2.1.1) seem unbothered, but lynx tried
> to decompress the page with gzip and failed miserably. Setting "
> reply-compressed-data = no" did not make any difference as this is the
> default.
> Any idea what might be wrong with my setup?
You don't say what version you have upgraded from.
If it was version 2.6b then I don't expect any changes since the
compression code was in that version. The only problem would be if
you have not enabled the compression in this version.
If it was version 2.5c or before then it is possible that there are
some pages in the cache that are already compressed. Before version
2.5d WWWOFFLE didn't block the Accept-Encoding header on outgoing
requests so it was possible for some compressed pages to be in the
cache already.
You also don't say how you know that it is the gzip header that is
causing the problem. The "reply-compressed-data = no" option is the
one correct one to stop WWWOFFLE from compressing the data.
You could try running 'wwwoffle -O <URL>' and see what you get. This
should not be compressed or have the 'Content-Encoding' header since
the wwwoffle program never asks for compressed data.
In all cases (when it is working correctly) there should only be a
gzip content encoding when the browser says that it can accept it.
(See the README.compress file for problems with this in some
browsers).
WWWOFFLE will only cache files in the uncompressed state. Any pages
that it receives that are already compressed will be uncompressed if
WWWOFFLE asked for compressed versions. If the server is sending
compressed data without WWWOFFLE asking for it then that is a server
problem.
Can you run wwwoffle with more debugging and capture the output.
Assuming that you are running the Bourne shell then try:
wwwoffled -d 6 -c wwwoffle.conf 2>&1 > wwwoffle.log
This will create a log file with all of the outgoing and incoming
requests.
When you find a problem URL get the pid from the logfile (it is in
square brackets in the following line):
wwwoffles[3592] Information: URL='http://localhost:8080/index/'.
and run the script from the WWWOFFLE source kit:
wwwoffle/contrib/logfile/log-pid.pl 3592 < wwwoffle.log
This will show you all the messages for that request. You can then
see the headers that are written to the server and the cache. (Note
that the headers that it displays as read from the server will exclude
'Content-Encoding' if WWWOFFLE is working as I expect it to.)
--
Andrew.
----------------------------------------------------------------------
Andrew M. Bishop [EMAIL PROTECTED]
http://www.gedanken.demon.co.uk/
WWWOFFLE users page:
http://www.gedanken.demon.co.uk/wwwoffle/version-2.6/user.html
