[
https://issues.apache.org/jira/browse/SOLR-856?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12649874#action_12649874
]
Hoss Man commented on SOLR-856:
-------------------------------
bq. Now I am more or less convinced that we must not add a filter. We should
have enough documentation on how these things are efficiently handled in each
of the containers.
If that's the consensus then i'm okay with that, but my personal preference
would be to do it in a container agnostic manner (by explicitly using a Filter
that does this in the stock web.xml) so that it works well for all users,
regardless of container, out of the box. users who are knowledgeable about
java, servlet containers, load balancers, etc... can then comment that filter
out of the web.xml (or replace it with something else)
punting on this to the servlet container puts a burden on novice users that
seems easily avoidable.
But it's not really that big of a deal to me -- it's an optimization that's
only really useful in low bandwidth situations anyway, so if it's something
that's going to make a difference to people, it's probably fine to make them
figure out the best way to turn it on in their specific situation.
So .... is this a "Won't Fix" situation?
> 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.
