lucene-solr-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Reyes, Mark" <Mark.Re...@bpiedu.com>
Subject Re: Client-side proxy for Solr 4.5.0
Date Wed, 27 Nov 2013 14:13:15 GMT
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.jelsma@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.Reyes@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.
Mime
View raw message