> detect deflated content -> inflate content -> re-deflate content -> do
> something appropriate with content length headers

> Any thoughts on the best way to go about this?

>> I see that there is a Plack::Middleware::Deflater, which seems to be
>> the opposite of what might be required to get the debug panels to work
>> on deflated content.  If I were to put something together to inflate
>> deflated content before manipulating it, is
>> Plack::Middleware::Deflater the correct template for something like
>> this?  I guess the process would be something like:

>> detect deflated content -> inflate content -> re-deflate content -> do
>> something appropriate with content length headers

>> Any thoughts on the best way to go about this?

> It sounds like an overly complicated processing to gain nothing. When
> you enable Debug you're obviously on the development, and enabling
> gzip compression on the development doesn't make much sense.

> On the other hand you can use Deflater middleeware *outside* Debug, so
> your application gives uncompressed content, filtered with the Debug
> panel and then Deflater to compress with the gzip encoding.

> ...
> use Plack::App::Proxy;

> use Plack::Builder;

> builder {
>    enable 'SimpleContentFilter', filter => sub {
>        s{</body>}{analytics code here</body>};
>    };

>    Plack::App::Proxy->new( remote => 'http://www.example.com/' )
>        ->to_app;

> };
> ...

> First off, I have read the note about SimpleContentFilter being a demo.  :)  Now, this works very well for me when proxying a site which is not deflating content.  However, if I try to proxy a site which is running Apache + mod_deflate, I can't mangle the content and the code just doesn't work.