Uploaded image for project: 'Trapperkeeper'
  1. Trapperkeeper
  2. TK-429

gzip encoding errantly disabled in tk-jetty9 when access-log-config enabled

    Details

    • Type: Bug
    • Status: Resolved
    • Priority: Normal
    • Resolution: Fixed
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: None
    • Labels:
    • Template:
    • Team:
      Systems Engineering
    • Story Points:
      1
    • Sprint:
      SE 2017-01-11
    • QA Risk Assessment:
      Needs Assessment

      Description

      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.

        Attachments

          Issue Links

            Activity

              People

              • Assignee:
                jeremy.barlow Jeremy Barlow
                Reporter:
                jeremy.barlow Jeremy Barlow
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved:

                  Zendesk Support