[TK-429] gzip encoding errantly disabled in tk-jetty9 when access-log-config enabled Created: 2017/01/10  Updated: 2018/02/07  Resolved: 2017/01/10

Status: Resolved
Project: Trapperkeeper
Component/s: None
Affects Version/s: None
Fix Version/s: None

Type: Bug Priority: Normal
Reporter: Jeremy Barlow Assignee: Jeremy Barlow
Resolution: Fixed Votes: 0
Labels: maintenance
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original Estimate: Not Specified

Issue Links:
relates to SERVER-2118 Catalogs are not gzipped Closed
relates to PUP-7251 gzip decompression mangles utf-8 cont... Closed
Team: Systems Engineering
Story Points: 1
Sprint: SE 2017-01-11
QA Risk Assessment: Needs Assessment


When the access-log-config setting is enabled in the webserver configuration for the trapperkeeper-webserver-jetty9 service and gzip-enabled is set to true, the tk-jetty9 service erroneously never uses gzip encoding to enable the response - even if the client specifically provides an "Accept-Encoding: gzip" header and the size of the response is greater than the minimum size that Jetty's GzipHandler uses as a threshold to encode, 256 bytes. The response is properly gzip encoded by the server with the same conditions, only with the access-log-config setting not present in the configuration.

Comment by Jeremy Barlow [ 2017/01/10 ]

Merged to trapperkeeper-webserver-jetty9#master at dcf31b46.

Comment by Jeremy Barlow [ 2017/01/10 ]

Jenkins job passed after the ticket was merged so marking this resolved.

Generated at Sun May 31 14:09:20 PDT 2020 using Jira 8.5.2#805002-sha1:a66f9354b9e12ac788984e5d84669c903a370049.