knox-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Larry McCay (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (KNOX-732) Knox does not recompress javascript resources
Date Thu, 08 Sep 2016 16:34:21 GMT

    [ https://issues.apache.org/jira/browse/KNOX-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15474339#comment-15474339
] 

Larry McCay commented on KNOX-732:
----------------------------------

While this may address the size difference between proxying through Knox and going direct,
it more than likely makes it impossible to rewrite the content of the JS. If there are embedded
URLs within the JS it would need to be rewritten to go through Knox rather than to the original
URL.

Unfortunately, I believe that we need to use an implementation that recompresses the content
rather than not ever decompressing it.

> Knox does not recompress javascript resources
> ---------------------------------------------
>
>                 Key: KNOX-732
>                 URL: https://issues.apache.org/jira/browse/KNOX-732
>             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
(v6.3.4#6332)

Mime
View raw message