Item13375: invalid content encoding using firefox http/2
Current State: Closed
Released In: 2.0.0
Target Release: major
Applies To: Engine
Using http/2 firefox does not clearly indicate that content is to be compressed using the
http header. Chrome does so, Firefox not. This is due to both not agreeing on being explicit on the implicit requirement for compression in http/2 transactions. One way to mitigate this is to let the http web server add a 'SPDY' header to the call to the Foswiki backend in case the transaction is a http/2. However the core did not properly read the ENV configuration under each and every circumstances thus setting a wrong content encoding for the response.
- 15 Apr 2015