Hi pub
You need to google CORS cross origin resource sharing. But no need to worry
about CORS if all of the JavaScript for the Solr site is on the Solr server.
But as others have said, it is best to have some PHP or Python UI in front of
Solr.
Cheers
Rick
On March 8, 2017 2:11:36 PM EST,
On 3/8/2017 12:11 PM, pubdiverses wrote:
> I have a site https://site.com under Apache.
> On the same physical server, i've installed solr.
>
> Inside https://site.com, i've a search form wich call solr with
> http://xxx.xxx.xxx.xxx/solr.
>
> But the browser says : "mixt content" and blocks the
ubdiverses [mailto:pubdiver...@free.fr]
Sent: Thursday, 9 March 2017 8:12 a.m.
To: solr-user@lucene.apache.org
Subject: Re: https
Hello,
I give you some more explanation.
I have a site https://site.com under Apache.
On the same physical server, i've installed solr.
Inside https://site.com, i've a search
Hello,
I give you some more explanation.
I have a site https://site.com under Apache.
On the same physical server, i've installed solr.
Inside https://site.com, i've a search form wich call solr with
http://xxx.xxx.xxx.xxx/solr.
But the browser says : "mixt content" and blocks the call.
>The first advise is NOT to expose your Solr directly to the public.
>Anyone that can hit /search, can also hit /update and wipe out your index.
I would second that too. We have never exposed Solr and I also sanitise queries
in the proxy.
Notice: This email and any attachments are confidential
On 3/7/2017 1:45 PM, pubdiverses wrote:
I would like to acces my solr instance with https://domain.com/solr.
how to do this ?
The reference guide covers this.
https://cwiki.apache.org/confluence/display/solr/Enabling+SSL
If you want to change the port to 443 so it will work without a port
The first advise is NOT to expose your Solr directly to the public.
Anyone that can hit /search, can also hit /update and wipe out your
index.
Unless you run a proper proxy that secures URLs and sanitizes the
parameters (in GET, in POST, escaped, etc). And if you are doing
that, you can setup
On 9/2/2014 11:44 AM, Christopher Gross wrote:
OK -- so I think my previous attempts were causing the problem.
Since this is a dev environment (and is still empty), I just went ahead and
wiped out the version-2 directories for the zookeeper nodes, reloaded my
solr collections, then ran that
Shawn,
How do I remove a collection from the SolrCloud? I tried making
testcollection and it failed, but now it is listed on the Graph part of
the Cloud page for my Solr instances. I tried using the delete on zkCli
but it still remains on that page. The only reliable thing that I've found
is to
Chris,
Did you try the Collections API to do whatever you're trying to do? 1.
Create collection and 2. Delete collection.
https://cwiki.apache.org/confluence/display/solr/Collections+API#CollectionsAPI-api6
The collection APIs cleanup things if stuff goes wrong. As I don't know,
I'm not sure
The DELETE from the collections API does get rid of it. Guess I glossed
over on that when I was looking over that section.
Still -- if the CREATE fails, I don't think it should create anything that
you'd need to go back and DELETE.
Thanks Anshum.
-- Chris
On Thu, Sep 4, 2014 at 3:02 PM,
I'm just curious, do you know why the CREATE failed for you?
On Thu, Sep 4, 2014 at 12:21 PM, Christopher Gross cogr...@gmail.com
wrote:
The DELETE from the collections API does get rid of it. Guess I glossed
over on that when I was looking over that section.
Still -- if the CREATE fails,
I was running 4.8.1, and the solr.ssl.checkPeerName flag didn't work, so it
was unable to talk to the other nodes to create the collection. I've since
upgraded to 4.9.0 and was able to create it, but I had to increment the
name. I've had other failures in the past as well, like typos
Once I upgraded to 4.9.0, the solr.ssl.checkPeerName option was used, and I
was able to create a collection.
I'm still wondering if there is a good way to remove references to any
collections that didn't complete, but block a collection from being made
with the same name?
Thanks!
-- Chris
On
Getting closer.
I can at least get the file to be there, but I can't figure out what to put
into it.
I make a clusterprops.json file, and its had:
{ urlScheme: https }
{ \urlScheme\: \https\ }
{ \\urlScheme\\: \\https\\ }
Which gets loaded in like this:
./zkCli.sh -zkhost localhost:2181 -cmd put
First question: ignoring the oiginal jira (which may be out of date
due to later improvements) have you seen the instructions?
https://cwiki.apache.org/confluence/display/solr/Enabling+SSL#EnablingSSL-SolrCloud
: I always get a message like this:
: Caused by:
Hi Hoss.
I did finally stumble onto that document (just after I posted my last
message, of course).
Using bash shell.
I've now tried those steps:
Tomcat is stopped.
First I run:
./zkcli.sh -zkhost localhost:2181 -cmd put /clusterprops.json
'{urlScheme:https}'
I confirm via the
Side note -- I've also tried adding the clusterprops.json file via
zookeeper's shell client on the command line, and within that client, all
with no luck.
-- Chris
On Tue, Sep 2, 2014 at 12:19 PM, Christopher Gross cogr...@gmail.com
wrote:
Hi Hoss.
I did finally stumble onto that document
: ./zkcli.sh -zkhost localhost:2181 -cmd put /clusterprops.json
: '{urlScheme:https}'
...
: Next I start Tomcat, I get this:
: 482 [localhost-startStop-1] ERROR org.apache.solr.core.SolrCore รข
: null:org.noggit.JSONParser$ParseException: JSON Parse Error:
: char=',position=0 BEFORE='''
OK -- so I think my previous attempts were causing the problem.
Since this is a dev environment (and is still empty), I just went ahead and
wiped out the version-2 directories for the zookeeper nodes, reloaded my
solr collections, then ran that command (zkcli.sh in the solr distro).
That did work.
Is the solr.ssl.checkPeerName option available in 4.8.1? I have my Tomcat
starting up with that as a -D option, but I'm getting an exception on
validating the hostname w/ the cert...
-- Chris
On Tue, Sep 2, 2014 at 1:44 PM, Christopher Gross cogr...@gmail.com wrote:
OK -- so I think my
21 matches
Mail list logo
