Am Montag, 17. November 2008 09:35 schrieb Andreas Hartmann: > Hi Wolfgang > > Wolfgang Jeltsch schrieb: > > I run Lenya 2.0.2 with Tomcat 5.5.27. I access Tomcat through a proxy > > which is an Apache 2.2.3 HTTP server. Communication between the proxy > > and Tomcat is done via AJP. The proxy maps URL paths beginning with /cms > > onto Tomcat paths beginning with /lenya. > > > > Now, I have many lines in the HTTP server’s error.log, containing: > > > > File does not exist: /var/www/lenya, > > referer: > > https://<mydomain>/cms/<mypublication>/authoring/css/page.css > > > > Seems as if something uses the internal Tomcat paths instead of the > > public URL paths. However, although page.css seems to be the problem > > source, the file > > $TOMCAT_HOME/webapps/lenya/lenya/pubs/default/resources/shared/css/page.c > >ss doesn’t seem to contain any references to /lenya. > > > > On the other hand, it contains lots of absolute paths which neither start > > with /lenya nor with /cms. Is this intended and how does this work? > > this is explained here: > > http://lenya.apache.org/docu20/reference/urls-and-links/link-management.htm >l > > There's a dedicated section about URLs in CSS files.
Hello Andreas, thanks for the link. However, this path/URL rewriting doesn’t work as it should. A path /my/path inside the CSS is rewritten to /lenya/my/path, probably because /lenya is the base path (servlet context?) for Lenya in Tomcat. But I use proxying and instead of /lenya/my/path I should get /cms/my/path since https://myserver/cms is mappend onto Tomcat’s /lenya. Why doesn’t it work like this? Best wishes, Wolfgang --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
