Return-Path: X-Original-To: apmail-lucene-solr-user-archive@minotaur.apache.org Delivered-To: apmail-lucene-solr-user-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A55CA10B89 for ; Fri, 22 Nov 2013 14:40:35 +0000 (UTC) Received: (qmail 1690 invoked by uid 500); 22 Nov 2013 14:40:28 -0000 Delivered-To: apmail-lucene-solr-user-archive@lucene.apache.org Received: (qmail 1585 invoked by uid 500); 22 Nov 2013 14:40:27 -0000 Mailing-List: contact solr-user-help@lucene.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: solr-user@lucene.apache.org Delivered-To: mailing list solr-user@lucene.apache.org Received: (qmail 1573 invoked by uid 99); 22 Nov 2013 14:40:26 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 14:40:26 +0000 X-ASF-Spam-Status: No, hits=-2.3 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of Gil.Hoggarth@bl.uk designates 194.66.236.30 as permitted sender) Received: from [194.66.236.30] (HELO w2k3-bspex1.bl.uk) (194.66.236.30) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Nov 2013 14:40:21 +0000 X-MimeOLE: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: How to work with remote solr savely? Date: Fri, 22 Nov 2013 14:39:56 -0000 Message-ID: <74C97E7DF5A7784D997217FF75D1216612AE1FB2@w2k3-bspex1> In-Reply-To: <528F68F7.2060102@delisavas.de> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: How to work with remote solr savely? thread-index: Ac7njpCXztbUQu/iQRyBQCkuq91mFQAAZl/g References: <528F68F7.2060102@delisavas.de> From: "Hoggarth, Gil" To: X-Virus-Checked: Checked by ClamAV on apache.org We solved this issue outside of Solr. As you've done, restrict the server to localhost access to Solr, add firewall rules to allow your developers on port 80, and proxypass allowed port 80 transfer to Solr. Remember to include the proxypassreverse too. (This runs on linux and apache httpd btw.) -----Original Message----- From: Stavros Delisavas [mailto:stavros@delisavas.de]=20 Sent: 22 November 2013 14:24 To: solr-user@lucene.apache.org Subject: How to work with remote solr savely? Hello Solr-Friends, I have a question about working with solr which is installed on a remote server. I have a php-project with a very big mysql-database of about 10gb and I am also using solr for about 10,000,000 entries indexed for fast search and access of the mysql-data. I have a local copy myself so I can continue to work on the php-project itself, but I want to make it available for more developers too. How can I make solr accessable ONLY for those exclusive developers? For mysql it's no problem to add an additional mysql-user with limited access. But for Solr it seems difficult to me. I have had my administrator restrict the java-port 8080 to localhost only. That way no one outside can access solr or the solr-admin interface. How can I allow access to other developers without making the whole solr-interface (port 8080) available to the public? Thanks, Stavros