[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[jetty-users] proxy: GzipContentTransformer and Content-Length headers
|
I'm trying to use the GzipContentTransformer to implement transparent gzip-ing of our backend responses.
It looks like the code handles the actual compression fine, but does not handle changing the HTTP headers to match the transformed input.
Additionally, there's multiple 'styles' of transparent gzipping, the "incorrect" widely-accepted 'Content-Encoding' and the not-widely-supported-but-more-correct Transfer-Encoding approach.
Once you start digging in to exactly what to do, you also have to start munging ETags.
Then you find a long history of both nginx and mod_deflate[1] getting it wrong...
Does the Jetty community have an example, or any recommendations?
I looked for uses of GzipContentTransformer but didn't find any samples.
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=39727
Attachment:
signature.asc
Description: Message signed with OpenPGP using GPGMail
