lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alexandre Rafalovitch (JIRA)" <>
Subject [jira] [Commented] (SOLR-12292) Make it easier to configure Solr with CORS
Date Fri, 04 May 2018 21:27:00 GMT


Alexandre Rafalovitch commented on SOLR-12292:

JSONP is read-only though. So, it exposes less than CORS.

IF CORS is open than any webpage can hit the localhost and possibly inject stuff, creating
a local exploit. 

This _may_ be possible with our implementation of JSONP as well, but the risk surface is much

> Make it easier to configure Solr with CORS
> ------------------------------------------
>                 Key: SOLR-12292
>                 URL:
>             Project: Solr
>          Issue Type: Improvement
>      Security Level: Public(Default Security Level. Issues are Public) 
>          Components: Server
>            Reporter: Jan Høydahl
>            Priority: Major
> 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 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.

This message was sent by Atlassian JIRA

To unsubscribe, e-mail:
For additional commands, e-mail:

View raw message