From: Adam R. <ad...@ex...> - 2010-01-05 13:02:29
|
2010/1/5 claud108 <cla...@ya...>: > > Joe, > > I wrote here: > (I'm shooting for a pure-Jetty/eXist solution, > with no Cocoon or Apache involved.) > > 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? 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... > Thank you, > Claudius > -- > View this message in context: http://old.nabble.com/URL-Rewriting---via-Jetty%27s-Rewrite-Handler-or-XQueryURLRewrite--tp20771719p27026601.html > Sent from the exist-open mailing list archive at Nabble.com. > > > ------------------------------------------------------------------------------ > 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 > -- Adam Retter eXist Developer { United Kingdom } ad...@ex... irc://irc.freenode.net/existdb |