Uploaded image for project: 'JBoss Enterprise Application Platform'
  1. JBoss Enterprise Application Platform
  2. JBEAP-5285

(7.1.0) access log states incorrect sizes for gzipped resources

    XMLWordPrintable

Details

    Description

      I have a css resource that weighs in at exactly 494750 bytes.
      It's served gzipped by the filter configured in the server config:

      <filter-ref name="gzip-filter" predicate="regex[pattern='(?:application/javascript|text/css)(;.*)?', value=%{o,Content-Type}, full-match=true]"/>
...
<gzip name="gzip-filter"/>

      When this css is served, access log's %b says 499002, whereas Chrome's devtools say 44.5 KB. So %b states that the uncompressed file was sent.
      The 494750 != 499002 disrepancy is probably due to JSF's EL evaluation of #{resource[...]} expressions, and is irrelevant here.

      Attachments

        Issue Links

          is blocked by

          Bug - A problem that impairs or prevents the functions of the product. UNDERTOW-568 access log states incorrect sizes for gzipped resources

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Resolved
          is cloned by

          Bug - A problem that impairs or prevents the functions of the product. JBEAP-4821 (7.0.z) access log states incorrect sizes for gzipped resources

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Verified
          is incorporated by

          Component Upgrade - A task tracking an update to a bundled component or revision of component upstream of the project. JBEAP-5284 (7.1.0) Upgrade Undertow from 1.3.23.Final to 1.4.0.CR4

          • Blocker - To be worked above all other priorities. This term is chosen when the severity of the issue is very high, has no workaround, or the effort for the change is comparatively low. Issues that may be very publicly visible and could generate significant media attention may also drive a higher priority.
          • Verified

          Activity

            People

              sdouglas1@redhat.com Stuart Douglas
              rhn-cservice-bbaranow Bartosz Baranowski
              Jan Stourac Jan Stourac
              Jan Stourac Jan Stourac
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: