[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368641#comment-16368641 ] Jan Høydahl commented on SOLR-10999: Go ahead! > 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 >Assignee: Jan Høydahl >Priority: Major > Labels: compression, http-headers, standards > Fix For: master (8.0), 7.3 > > 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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16368404#comment-16368404 ] Michael Braun commented on SOLR-10999: -- [~janhoy] sorry for the delay in getting back with you after chatting about this at LSR 2017 - can I update your patch for the Jetty 9.4 version? > 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 >Assignee: Jan Høydahl >Priority: Major > Labels: compression, http-headers, standards > Fix For: master (8.0), 7.3 > > 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 (v7.6.3#76005) - To unsubscribe, e-mail: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16148684#comment-16148684 ] Jan Høydahl commented on SOLR-10999: I'm stopping progress on this since I won't be able to work on it for a few months. Anyone feel free to grab and improve, even assign yourself :) > 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 >Assignee: Jan Høydahl > Labels: compression, http-headers, standards > Fix For: 7.1 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080422#comment-16080422 ] Michael Braun commented on SOLR-10999: -- [~janhoy] just to put the modules in one place and make easier to disable potentially, but this makes sense too. > 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 >Assignee: Jan Høydahl > Labels: compression, http-headers, standards > Fix For: 7.1 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16080174#comment-16080174 ] Jan Høydahl commented on SOLR-10999: [~mbraun688] any comment to the benefit of setting module in start script? > 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 >Assignee: Jan Høydahl > Labels: compression, http-headers, standards > Fix For: 7.1 > > 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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[ https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=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: dev-unsubscr...@lucene.apache.org For additional commands, e-mail: dev-h...@lucene.apache.org
[jira] [Commented] (SOLR-10999) Support "Accept-Encoding" header to enable response gzip compression
[
https://issues.apache.org/jira/browse/SOLR-10999?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16072830#comment-16072830
]
Michael Braun commented on SOLR-10999:
--
Instead of placing into solr-jetty-context.xml, is embedding into the solr
start script like is done with ssl possible? (ssl example below):
{code}
SOLR_JETTY_CONFIG+=("--module=https")
{code}
> 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: master (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: dev-unsubscr...@lucene.apache.org
For additional commands, e-mail: dev-h...@lucene.apache.org
