[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-tabpanelfocusedCommentId=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.
[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-tabpanelfocusedCommentId=12599201#action_12599201 ] Hoss Man commented on SOLR-506: --- Assuming some form of SOLR-505 is committed the most straightforward way to make caching configurable per handler instance is probably to add an optional init param to RequestHandlerBase 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 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.
[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-tabpanelfocusedCommentId=12599208#action_12599208 ] Shalin Shekhar Mangar commented on SOLR-506: Why didn't I think of that? :) Yes, I agree, that should be the most painless way of implementing this. 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 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.
