Hi, Inspired by SOLR-10981 "Allow update to load gzip files” where the proposal is to obey the Content-Encoding HTTP request header to update a compressed stream, I started looking at other headers to do things in more industry-standard ways.
Accept: Advertises which content types, expressed as MIME types, the client is able to understand https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Accept Could replace or at least be an alternative to “wt”. Examples: Accept: application/xml Accept: text/csv Issue: Most browsers sends a long accept header, typically application/xml,text/html,*/*, and now that json is default for Solr, we’d need to serve JSON if the accept header includes “*/*" 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 What do you think? -- Jan Høydahl, search solution architect Cominvent AS - www.cominvent.com --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
