Yeah I prefer a whitelist of locked down query request handlers via a
proxy that are reasonably well protected. I would never expose update to
the web or allow any updating over a public interface.
If you want an example, you can checkout
http://solr.quepid.com/solr/statedecoded/select?q=*:*&qt=u
If you are using Linux a simple one liner in IP tables
iptables -I INPUT \! --src www.yourwebserver.com -m tcp -p tcp --dport
8983 -j DROP
If windows, you can do something similar
otherwise it is very easy for anyone to delete all your documents with
http://yoursolrserver.com:8983/solr/your-co
Hi Shawn
Maybe I should have qualified the parameters of scenarios this make me
comfortable just proxying Solr directly w/o an API
These situations include:
1. I've got no qualms about giving the whole world access to every document
in the index. There's nothing protected about anything.
2. The
On 12/25/2015 12:17 PM, Eric Dain wrote:
> Does allowing javascript direct access to SolrCloud raise security concern?
> should I build a REST service in between?
>
> I need to provide async search capability to web pages. the pages will be
> public with no authentication.
End users should never
I would put in a basic iptables statement to allow only your webserver to
prevent
http://172.16.0.22:8983/solr/products/update?stream.body=%3Cdelete%3E%3Cquery%3E*:*%3C/query%3E%3C/delete%3E&commit=true
On 25 December 2015 at 14:58, Eric Dain wrote:
> Thanks, that is very helpful.
>
> Have you
Thanks, that is very helpful.
Have you tried denying access to some fields in the documents?
On Fri, Dec 25, 2015 at 11:31 AM, Doug Turnbull <
dturnb...@opensourceconnections.com> wrote:
> We do this all the time, whitelisting only the readonly search end points
> we want to support and disallow
We do this all the time, whitelisting only the readonly search end points
we want to support and disallowing excessively large paging.
Here is a template for an nginx solr proxy. The read me describes more of
our philosophy
https://github.com/o19s/solr_nginx
On Friday, December 25, 2015, Eric Da
Hi all,
Does allowing javascript direct access to SolrCloud raise security concern?
should I build a REST service in between?
I need to provide async search capability to web pages. the pages will be
public with no authentication.
Happy searching,
Eric
Hi Elvis,
We're having a similar problem with one of our cloud setups.
I'm currently running Solr 4.10.4 with 2 shards and no replicas. One of our
shards also keeps dropping off with the same error message. This happens
because the shard executes too many full GCs which completely freezes the
machi
Do you have a full stack trace? A bit hard to help without that.
On 24 Dec 2015 2:54 pm, "Midas A" wrote:
> Hi ,
>
>
> Please provide the steps to resolve the issue.
>
>
> com.mysql.jdbc.exceptions.jdbc4.MySQLNonTransientConnectionException:
> Communications link failure during rollback(). Transa
my environment is solrcloud 5.2.0, 3 shards, every shard has 2 replica,one
leader,one replica
[11-18 06:58:42.515][ERROR]
org.apache.solr.common.SolrException.log(SolrException.java:139) -
org.apache.solr.common.SolrException: no servers hosting shard:
at
org.apache.solr.handler.compone
11 matches
Mail list logo
