Re: [Exist-open] Tidyup URL

[Joseph T. <to...@li...>]

On Jun 18, 2010, at 1:37 PM, Adam Retter wrote:

>>> Another common approach is to reverse proxy behind your webserver, an
>>> example is provided here -
>>> http://www.exist-db.org/production_web_proxying.html
>> 
>> I just looked at that link and the page seems to be incomplete, i.e., it looks like it was truncated.
>> There isn't an example for Apache even though it talks about there being one, and what's there
>> I can only guess from it's brevity is the start of an example for nginx .  FYI.  I'd sure like to see the
>> rest of that page as I have a project that involves running multiple sites off of one eXist instance and
>> I'm guessing this is where I would start.
> 
> The nginx example is complete. Nginx has a very simple configuration,
> its designed to be a very lightweight and efficient server.

Oh, that's cool. I've never really used nginx before. Is there a similar example for Apache?


> 
>> This is a little off of Nigel's question, but is it possible to do this without the proxy, just using virtual hosting in Jetty
>> that points to a specific collection? All the Jetty docs I've seen claim that you really don't need to front it with another
>> webserver, has that not been the collective experience here? I find I'm usually faced with a limited amount of memory,
>> so any process I can get rid of is a good thing.
> 
> Jetty isnt enough - You would also need URL rewriting such as the
> XQueryURLRewrite filter.

I was sort of guessing that part, but wanted to see if beyond that there was a reason not to go the standalone Jetty/virtual hosting route.
I think I saw an archived post from you where you said you did quite a lot of multiple sites on one eXist db setups. Do you usually use the
proxy method you outlined? If so, why?

											Thanks,
														J. Toman