Re: [OT] HTTP2 gzip compression and Safari browser

2019-05-09 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kirill, On 5/8/19 23:20, Kirill Ilyukhin wrote: > This might be a bad idea, but I have exactly the same issue with > static content (simple index.html file). Also BREACH vulnerability > implies three conditions, a webapp developer may decide to use

Re: [OT] HTTP2 gzip compression and Safari browser

2019-05-08 Thread Kirill Ilyukhin
Christopher, This might be a bad idea, but I have exactly the same issue with static content (simple index.html file). Also BREACH vulnerability implies three conditions, a webapp developer may decide to use TLS+gzip because one of them is not satisfied for a particular service. I suppose servers

Re: HTTP2 gzip compression and Safari browser

2019-05-08 Thread Mark Thomas
On 08/05/2019 13:27, Kirill Ilyukhin wrote: > Mark, > > Could you please take a closer look to the issue? This happens with Safari > and native apps on iOS 11 and iOS 12 which means that Tomcat HTTP/2 cannot > be enabled for any service with iOS clients. I've done all I can. The data passed back

Re:[OT] HTTP2 gzip compression and Safari browser

2019-05-08 Thread Christopher Schultz
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Kirill, Is it a good idea to use TLS+gzip for dynamic services? http://breachattack.com/ ? - -chris On 5/8/19 08:27, Kirill Ilyukhin wrote: > Mark, > > Could you please take a closer look to the issue? This happens with > Safari and native apps

Re: HTTP2 gzip compression and Safari browser

2019-05-08 Thread Kirill Ilyukhin
Mark, Could you please take a closer look to the issue? This happens with Safari and native apps on iOS 11 and iOS 12 which means that Tomcat HTTP/2 cannot be enabled for any service with iOS clients. If we open https://www.google.com in Safari (both iOS and Mac OS), we see that HTML and JS are r

Re: HTTP2 gzip compression and Safari browser

2019-05-08 Thread Mark Thomas
Although I find it hard to believe, this looks like a browser bug. There is a similar issue with FireFox: https://bz.apache.org/bugzilla/show_bug.cgi?id=63354 I suggest opening an issue with Apple. Mark On 08/05/2019 05:23, Kirill Ilyukhin wrote: > Hi, > > I am trying to run Tomcat with HTTP/

HTTP2 gzip compression and Safari browser

2019-05-07 Thread Kirill Ilyukhin
Hi, I am trying to run Tomcat with HTTP/2 support. Everything works perfectly fine until I enable content compression. Google Chrome on Mac OS is OK with gzip compression. Apple Safari on Mac OS and iOS fail with “The operation couldn’t be completed. Protocol error” (NSPOSIXErrorDomain:100). iOS U