[
https://issues.apache.org/jira/browse/KNOX-732?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15479900#comment-15479900
]
Larry McCay commented on KNOX-732:
----------------------------------
I have a better idea of what that is about now.
It seems that the GzipHandler is a decorator that will compress the content for
the indicated types and methods for the contexts associated with the handler
provided in setHandler().
I didn't think that the correlationHandler is the right one to use there though
it may work in a round about way - not sure.
I was thinking that setting the handler to be "contexts" as is done for the
TraceHandler was probably the way to go.
I believe that the contexts represented by that collection are all the topology
specific contexts deployed to the server.
Since the correlationHandler is wrapping the traceHandler which is given the
contextsCollection as the handler it may just work.
I can't exactly tell by your previous comment whether you have observed it
working properly for JS files such as required for proxying UIs like Ambari.
Have you tried it out?
Thanks, [~smore]!
> 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.9.1
> Reporter: Sumit Gupta
> Assignee: Sandeep More
> Fix For: 0.10.0
>
> Attachments: KNOX-732.001.patch, KNOX-732.002.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)
