[
https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16072872#comment-16072872
]
Jan Høydahl commented on SOLR-10999:
------------------------------------
Guess that could be possible, if it is any point at all to make it possible to
remove it? The client can already control when to trigger compression with the
Accept-Encoding header, so why would we want to disable the handler?
> Support "Accept-Encoding" header to enable response gzip compression
> --------------------------------------------------------------------
>
> Key: SOLR-10999
> URL: https://issues.apache.org/jira/browse/SOLR-10999
> Project: Solr
> Issue Type: Improvement
> Security Level: Public(Default Security Level. Issues are Public)
> Components: Server
> Reporter: Jan Høydahl
> Labels: compression, http-headers, standards
> Fix For: 7.0
>
> Attachments: SOLR-10999.patch
>
>
> Spinoff from
> [email|https://lists.apache.org/thread.html/b4ec90b01bc075a98947e77b0a683308f760221dccb11be5819d1601@%3Cdev.lucene.apache.org%3E]
> Accept-Encoding:
> Advertises which content encoding, usually a compression algorithm, the
> client is able to understand
> https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept-Encoding
> Could enable compression of large search results. SOLR-856 suggests that this
> is implemented,
> but it does not work. Seems it is only implemented for replication. I’d
> expect this to be useful for
> large /export or /stream requests. Example:
> Accept-Encoding: gzip
> Could be configured with the [Jetty Gzip
> Handler|http://www.eclipse.org/jetty/documentation/9.4.x/gzip-filter.html]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
