Re: [Exist-open] URL Rewriting - via Jetty's Rewrite Handler or XQueryURLRewrite?

[Vyacheslav S. <vya...@gm...>]

i did not see reasons to hide exist - even more i can suggest in some
cases to use eXist as proxy server for some reasons

2010/1/5 Joe Wicentowski <jo...@gm...>:
> Claudius,
>
>>> This means that on a production server one can use only eXist, without
>>> apache in front of it, as is suggested in eXist's documentation?
>
> Yes, one can - remember to take the usual security precautions
> outlined in http://exist-db.org/production_good_practice.html.
>
>> On web facing production server I would recommend using Apache HTTP or
>> Nginx upfront and reverse proxy eXist into the URI namespace. See the
>> production best practice bits in the documentation...
>
> Adam - in http://exist-db.org/production_web_proxying.html you
> explained the reasons behind the 'positive' reasons for adopting the
> reverse proxy approach (1. Unified web namespace and 2. Virtual
> Hosting), but could you expand a bit on the 'negative' reason: "eXist
> like any Web Application Server (Tomcat, WebLogic, GlassFish, etc)
> should not be directly exposed to the Web."  My understanding was that
> Jetty played the role of 'web server' to eXist's 'web application
> server', no?  Pardon my ignorance!
>
> Joe
>
> ------------------------------------------------------------------------------
> This SF.Net email is sponsored by the Verizon Developer Community
> Take advantage of Verizon's best-in-class app development support
> A streamlined, 14 day to market process makes app distribution fast and easy
> Join now and get one step closer to millions of Verizon customers
> http://p.sf.net/sfu/verizon-dev2dev
> _______________________________________________
> Exist-open mailing list
> Exi...@li...
> https://lists.sourceforge.net/lists/listinfo/exist-open
>