[Filterproxy-devel] Re: filterproxy bugs

[Bob M. <mce...@dr...>]

klas jarnefelt [bl...@dj...] wrote:
> i got the old version working again with some help from charon, though
> i'm still not exactly sure what the problem was.

Great!  My debian machine is far away right now, and I just realized
I've never actually done an apt-get install filterproxy.  I tried it,
and it failed.  :(  I'll deal with it when I get home in a month.

> the error with ultimatemetal.com+compress module seems to be opera
> only.  is there any way i can make it work with the compress module
> turned off?

Can you send me some log snippets or something?  It might be useful to
go into the Header module and turn on dumping headers to the log file,
and send me that.  The Compress module is enabled, and configured to
filter .* on the main page, right?

To get it to work without the Compress module, you have to configure
your browser not to send the
    Accept-Encoding: gzip
header, which just about all browsers send.  Alternatively you could
delete this header using FilterProxy's Header module.

If the server sees that header (and is configured to send compressed
content), it will send compressed content back to you.

> thanks a bunch for helping. =3D)

No prob.

Cheers,
-- Bob

Bob McElrath (rsm...@st...)=20
Univ. of Wisconsin at Madison, Department of Physics