Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
None
-
None
-
None
Description
While working on SOLR-8207 I wanted to collect info from other SolrCloud nodes from the AdminUI. However this is blocked by CORS policy. In that Jira I instead did the fan-out on the Solr server side for the two handler I needed.
It would be nice if all nodes in a SolrCloud cluster could automatically accept any other node as a legal origin, and make it easy for users to add other origins by config.
If we use the Jetty CORS filter in web.xml, perhaps we could parse a env.var from solr.in.xx and inject into the allowedOrigins property of that filter? There is also SOLR-6059 which tries to implement CORS inside of Solr handlers and not in Jetty. Don't know pros/cons of those.
Attachments
Issue Links
- is a child of
-
SOLR-14361 SIP-6 Solr should own the bootstrap process
- Open
- is related to
-
SOLR-6059 Basic support for Cross-Origin resource sharing (CORS) in search requests
- Open
-
SOLR-12282 JSONResponseWriter should return Content-Type application/javascript for JSONP requests
- Patch Available