knox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sandeep More (JIRA)" <>
Subject [jira] [Commented] (KNOX-732) Knox does not recompress javascript resources
Date Fri, 09 Sep 2016 15:39:21 GMT


Sandeep More commented on KNOX-732:

There are couple of ways Gzip can be added/configured in Jetty:

Using Gzip Handler (

    - This should be fairly easy to hook-up, probably just add to the existing list of handlers
and we should be done.
    - Recommended way going forward (over Gzip Filter )
    - Need to upgrade Jetty for this, currently Jetty is on 9.2.15.x and this feature is in
    - Need to refactor some code (e.g. in gateway-test-utils which depends on some classes
that current Jetty versions, 9.3.x +,  refactored)

Using the Gzip Filter (

    - No upgrades, no refactoring.
    - Gzip Filter is deprecated going forward.
    - Gzip Filter needs to be applied multiple places.

Or the other option is to backport Gzip Handler change, which might not be clean and we'll
have to throw it away once we upgrade Jetty.

Any preference, thoughts or biases ?


> Knox does not recompress javascript resources
> ---------------------------------------------
>                 Key: KNOX-732
>                 URL:
>             Project: Apache Knox
>          Issue Type: Bug
>          Components: Server
>    Affects Versions: 0.10.0
>            Reporter: Sumit Gupta
>            Assignee: Sandeep More
>             Fix For: 0.10.0
>         Attachments: KNOX-732.001.patch
> When using the Ambari UI proxy service it is observed that the app.js file is about 7MB
whereas it is much smaller (about 1MB) when the UI is not proxied by Knox. 
> A compression solution needs to be investigated. Possibly by adding a gzip compression
handler or filter to jetty.

This message was sent by Atlassian JIRA

View raw message