You are viewing a plain text version of this content. The canonical link for it is here.
Posted to solr-dev@lucene.apache.org by "Hoss Man (JIRA)" <ji...@apache.org> on 2008/06/18 20:32:45 UTC

[jira] Commented: (SOLR-506) Enabling HTTP Cache headers should be configurable on a per-handler basis

    [ https://issues.apache.org/jira/browse/SOLR-506?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12606029#action_12606029 ] 

Hoss Man commented on SOLR-506:
-------------------------------

the patch seems straight forward, but the default for RequestHandlerBase should be that http caching is "ok"

Request Handlers that can't be cached will enerally be the exception to the rule (and will probably hardcode setHttpCaching(false)) ... run of the mill custom request handlers that people write which subclass RequestHandlerbase should automaticly start supporting HTTP caching, and if the users of those handlers don't wnat caching they should explicitly turn it off (not vice versa)

> Enabling HTTP Cache headers should be configurable on a per-handler basis
> -------------------------------------------------------------------------
>
>                 Key: SOLR-506
>                 URL: https://issues.apache.org/jira/browse/SOLR-506
>             Project: Solr
>          Issue Type: Improvement
>    Affects Versions: 1.3
>            Reporter: Shalin Shekhar Mangar
>         Attachments: SOLR-506.patch
>
>
> HTTP cache headers are needed only for select handler's response and it does not make much sense to enable it globally for all Solr responses.
> Therefore, enabling/disabling cache headers should be configurable on a per-handler basis. It should be enabled by default on the select request handler and disabled by default on all others. It should be possible to override these defaults through configuration as well as through API.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.