James Smith wrote:
According to the documentation - mod_deflate should be being run after
my filter as mod_deflate is a connection filter where mine is request
filter!
My filter is being run - and getting the right input content - observed
as I was dumping the HTML coming in and going out!
Allright. I still don't feel like diving in your code, but for the sake
of someone else maybe :
- when mod_deflate is not in the picture, the output is the result of
the original output, modified by your filter, uncompressed.
- when mod_deflate is configured, then the output is compressed, but it
appears to be the unmodified original output, as if your filter was no
longer in the picture.
- however, in both cases, you can see that your filter runs and modifies
the original output data.
So it almost looks as if both your filter and mod_deflate get hold of
the original output data, and whatever your filter produces as output
just disappears into perl heaven..
Although I'm not still diving into your code, I seem to see somewhere in
it that it is also adding a response header. Does that response header
also disappear, or is it still in the mod_deflate output ?
