I'm having similar problems with mine, and I believe this falls back to a bug in Lenya where the /lenya/ prefix is hard-coded someplace that doesn't allow for >the mod_proxy setup to work when Lenya is used in conjuction with Tomcat in the ROOT context, or Jetty, which by default is installed in the ROOT >context. If you are in any one of these situations, then my understanding is that it won't be able to work the way it was intended to. Can a dev confirm this?
Thanks for the response. I'm running lenya with jetty behind Apache httpd. Apache provides ssl and reverse proxies to lenya using mod_proxy and mod_rewrite (pretty much a straight copy of the mod_proxy tuturials, (yours?). Apache also provides proxy to php application.
Would a better set up be to use jetty without apache, integrate ssl into jetty along with php
Would this solve the rewrite links problem? Lee C --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
