From dev-return-321124-archive-asf-public=cust-asf.ponee.io@lucene.apache.org Fri May 4 23:27:09 2018 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx-eu-01.ponee.io (Postfix) with SMTP id D261E180634 for ; Fri, 4 May 2018 23:27:08 +0200 (CEST) Received: (qmail 27564 invoked by uid 500); 4 May 2018 21:27:02 -0000 Mailing-List: contact dev-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@lucene.apache.org Delivered-To: mailing list dev@lucene.apache.org Received: (qmail 27551 invoked by uid 99); 4 May 2018 21:27:02 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd3-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 04 May 2018 21:27:02 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd3-us-west.apache.org (ASF Mail Server at spamd3-us-west.apache.org) with ESMTP id 2049A1807F2 for ; Fri, 4 May 2018 21:27:02 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd3-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -109.511 X-Spam-Level: X-Spam-Status: No, score=-109.511 tagged_above=-999 required=6.31 tests=[ENV_AND_HDR_SPF_MATCH=-0.5, KAM_ASCII_DIVIDERS=0.8, RCVD_IN_DNSWL_MED=-2.3, SPF_PASS=-0.001, T_RP_MATCHES_RCVD=-0.01, USER_IN_DEF_SPF_WL=-7.5, USER_IN_WHITELIST=-100] autolearn=disabled Received: from mx1-lw-us.apache.org ([10.40.0.8]) by localhost (spamd3-us-west.apache.org [10.40.0.10]) (amavisd-new, port 10024) with ESMTP id MVXmvWYEyrrd for ; Fri, 4 May 2018 21:27:01 +0000 (UTC) Received: from mailrelay1-us-west.apache.org (mailrelay1-us-west.apache.org [209.188.14.139]) by mx1-lw-us.apache.org (ASF Mail Server at mx1-lw-us.apache.org) with ESMTP id D4EFE5F47D for ; Fri, 4 May 2018 21:27:00 +0000 (UTC) Received: from jira-lw-us.apache.org (unknown [207.244.88.139]) by mailrelay1-us-west.apache.org (ASF Mail Server at mailrelay1-us-west.apache.org) with ESMTP id 64CE4E00D3 for ; Fri, 4 May 2018 21:27:00 +0000 (UTC) Received: from jira-lw-us.apache.org (localhost [127.0.0.1]) by jira-lw-us.apache.org (ASF Mail Server at jira-lw-us.apache.org) with ESMTP id 19B1A21291 for ; Fri, 4 May 2018 21:27:00 +0000 (UTC) Date: Fri, 4 May 2018 21:27:00 +0000 (UTC) From: "Alexandre Rafalovitch (JIRA)" To: dev@lucene.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (SOLR-12292) Make it easier to configure Solr with CORS MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/SOLR-12292?page=3Dcom.atlassian= .jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1646= 4413#comment-16464413 ]=20 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.=C2=A0 This _may_ be possible with our implementation of JSONP as well, but the ri= sk surface is much smaller. > Make it easier to configure Solr with CORS > ------------------------------------------ > > Key: SOLR-12292 > URL: https://issues.apache.org/jira/browse/SOLR-12292 > Project: Solr > Issue Type: Improvement > Security Level: Public(Default Security Level. Issues are Public)=20 > Components: Server > Reporter: Jan H=C3=B8ydahl > 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|https://en.wikiped= ia.org/wiki/Cross-origin_resource_sharing]=C2=A0policy. In that Jira I inst= ead 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|http://www.eclipse.org/jetty/documentati= on/9.4.9.v20180320/cross-origin-filter.html]=C2=A0in web.xml, perhaps we co= uld 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 C= ORS inside of Solr handlers and not in Jetty. Don't know pros/cons of those= . -- This message was sent by Atlassian JIRA (v7.6.3#76005) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org For additional commands, e-mail: dev-help@lucene.apache.org