Why complicate it?, I think the simplest solution to the poster question
is either a transparent proxy or proxy jetty (or tomcat) via Apache Web
Server.
I don't think there will be any difference between either, only how easy
one or the other are to implement.
HTH,
Guido.
On 27/11/13 14:13, Reyes, Mark wrote:
What about using some JSONP techniques since the results in the Solr
instance rest as key/value pairs?
On 11/26/13, 10:53 AM, "Markus Jelsma" <markus.jel...@openindex.io> wrote:
I don't think you mean client-side proxy. You need a server side layer
such as a normal web application or good proxy. We use Nginx, it is very
fast and very feature rich. Its config scripting is usually enough to
restrict access and limit input parameters. We also use Nginx's embedded
Perl and Lua scripting besides its config scripting to implement more
difficult logic.
-----Original message-----
From:Reyes, Mark <mark.re...@bpiedu.com>
Sent: Tuesday 26th November 2013 19:27
To: solr-user@lucene.apache.org
Subject: Client-side proxy for Solr 4.5.0
Are there any GOOD client-side solutions to proxy a Solr 4.5.0 instance
so that the end-user can see their queries w/o being able to directly
access :8983?
Applications/frameworks used:
- Solr 4.5.0
- AJAX Solr (javascript library)
Thank you,
Mark
IMPORTANT NOTICE: This e-mail message is intended to be received only
by persons entitled to receive the confidential information it may
contain. E-mail messages sent from Bridgepoint Education may contain
information that is confidential and may be legally privileged. Please
do not read, copy, forward or store this message unless you are an
intended recipient of it. If you received this transmission in error,
please notify the sender by reply e-mail and delete the message and any
attachments.
IMPORTANT NOTICE: This e-mail message is intended to be received only by
persons entitled to receive the confidential information it may contain. E-mail
messages sent from Bridgepoint Education may contain information that is
confidential and may be legally privileged. Please do not read, copy, forward
or store this message unless you are an intended recipient of it. If you
received this transmission in error, please notify the sender by reply e-mail
and delete the message and any attachments.
