On 1/26/2015 9:02 PM, Summer Shire wrote: > Running solr (4.7.2) locally and hitting the admin page like this works just > fine http://localhost:8983/solr/ <http://localhost:8983/solr/#># > <http://localhost:8983/solr/#> > > But on my deployment server my path is > http://example.org/jetty/MyApp/1/solr/# > <http://example.org/jetty/MyApp/1/solr/#> > Or http://example.org/jetty/MyApp/1/solr/admin/cores > <http://example.org/jetty/MyApp/1/solr/admin/cores> or > http://example.org/jetty/MyApp/1/solr/main/admin/ > <http://example.org/jetty/MyApp/1/solr/main/admin/> > > the above request in a browser loads the admin page half way and then spawns > another request at > http://example.org/solr/admin/cores <http://example.org/solr/admin/cores>…. > > how can I maintain my other params such as jetty/MyApp/1/ > > btw http://example.org/jetty/MyApp/1/solr/main/select?q=*:* > <http://example.org/jetty/MyApp/1/solr/main/select?q=*:*> or any other > requesthandlers work just fine.
Is this the scenario that got mentioned on the IRC channel? That was indicated to be behind a proxy. If Solr is behind a proxy that changes the URL path (which is the only way I can imagine this is working on port 80), the proxy must also rewrite the URLs that the Solr admin UI sends to the user's browser. Those URLs are embedded in the data (definitely javascript, and possibly html) that the admin UI sends to the user's browser, and are created by information available to Solr. Solr will have no idea what the path on the proxy is. Thanks, Shawn
