[
https://issues.apache.org/jira/browse/SOLR-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12648038#action_12648038
]
Erik Hatcher commented on SOLR-856:
-----------------------------------
For the record, I'm absolutely +1 on this being done by containers if the major
ones can do it.
It'd be interesting if the containers that are doing it would strip the gzip
accept header, that way it wouldn't matter if Solr had this in there or not....
but I doubt we're so lucky for that, eh?
Also worth noting is my take on "deployment descriptors". It was really
designed (though not implemented so well) to be tweaked at deploy-time. So it
would really be sufficient to document how to change web.xml to add in a filter
if needed, and where to obtain the JAR file... how to repackage a .war. Yeah,
it's a pain, but it does keep something that is obviously a separate concern
entirely separate, and not all that difficult to manage the "hard" way just
described.
Some containers, if I'm not mistaken, have control panels where .war deployment
descriptors can be managed, right?
> Suport for "Accept-Encoding : gzip" in SolrDispatchFilter
> ---------------------------------------------------------
>
> Key: SOLR-856
> URL: https://issues.apache.org/jira/browse/SOLR-856
> Project: Solr
> Issue Type: Improvement
> Reporter: Noble Paul
> Attachments: SOLR-856.patch
>
>
> If the client sends an Accept-Encoding : gzip header then SolrDispatchFilter
> should respect that and send back data as zipped
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
