any bug reported that pagespeed's inflation of compressed javascript file may have added one byte?

[Alex Wu]

This is from  what I observed from the lastest pagespeed (nearly). If I enabled apache's inflate module, js file is processed properly. If I disabled apache's inflate, there is one extra byte (space) added in the middle of javascript file. It is hard to debug since the compressed response is invoked. Once inflated from apache, it looks fine.

[Otto van der Schaaf]

That doesn't ring a bell with me. Does this reproduce easily? 

On Tue, Mar 14, 2017 at 10:45 PM Alex Wu <yw9...@gmail.com> wrote:

This is from  what I observed from the lastest pagespeed (nearly). If I enabled apache's inflate module, js file is processed properly. If I disabled apache's inflate, there is one extra byte (space) added in the middle of javascript file. It is hard to debug since the compressed response is invoked. Once inflated from apache, it looks fine.

--
You received this message because you are subscribed to the Google Groups "pagespeed-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pagespeed-de...@googlegroups.com.
To post to this group, send email to pagesp...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/pagespeed-dev/1c18f528-86d0-40da-b087-09f0ff63fde1%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.