Re: Tomcat 7.0: compression="on" or compression="force" running on Java 1.8.0_151 causes content encoding errors in browsers

2017-10-30 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 On 10/26/17 10:30 AM, Johan Compagner wrote: > They (oracle) first introduced this in Java9.. Its something that > they don't expect that certain things are reused/cached i believe > > Now they backported that same bug also to java 8, i think they

Re: Tomcat 7.0: compression="on" or compression="force" running on Java 1.8.0_151 causes content encoding errors in browsers

2017-10-26 Thread Johan Compagner
They (oracle) first introduced this in Java9.. Its something that they don't expect that certain things are reused/cached i believe Now they backported that same bug also to java 8, i think they already fixed it for the next java8 version: https://bugs.openjdk.java.net/browse/JDK-8189789 On

Re: Tomcat 7.0: compression="on" or compression="force" running on Java 1.8.0_151 causes content encoding errors in browsers

2017-10-26 Thread Jörg Schubert
Am 26.10.2017 um 15:36 schrieb Jörg Schubert: Hello, We have a very stange problem. Since updating java 8 to build 151 (x86-64), tomcat is producing illegal compressed responses - sometimes. Firefox and Chrome are complaining about content encoding errors. Firefox error message is: an

Tomcat 7.0: compression="on" or compression="force" running on Java 1.8.0_151 causes content encoding errors in browsers

2017-10-26 Thread Jörg Schubert
Hello, We have a very stange problem. Since updating java 8 to build 151 (x86-64), tomcat is producing illegal compressed responses - sometimes. Firefox and Chrome are complaining about content encoding errors. Firefox error message is: an invalid or unknown form of compression was used.