2012/6/5 Morgan, Russel <russel.mor...@disney.com>: > Tomcat Users: > > > > Has anyone found a graceful way to handle static content linking that works= > both pre and post the the following change? > > https://issues.apache.org/bugzilla/show_bug.cgi?id=3D50026
You mean https://issues.apache.org/bugzilla/show_bug.cgi?id=50026 (you e-mail formatting want wrong) > > We have quite a few customers on earlier versions of Tomcat 6 as well as ne= > w customers picking up later versions that are post this patch. I am looki= > ng for some kind of work around that works in both generations. > > > > Here is an example of what we are doing as far as static linking in our web= > app. > > > > So on older tomcat's (prior to 6.0.30) > > http://localhost:8080/cms/default/css/gopublish.css > > http://localhost:8080/cms/static/css/gopublish.css > > both work to hit items in the root of the webapp so .../cms(as webapp)/css/= > gopublish.css So, if I understand you, both addresses should hit http://localhost:7080/cms/css/gopublish.css There exists such feature as "URL rewriting". That is, you have to internally (on the server) redirect your URL to the correct address. It is easy to implement it as a Filter by yourself, but there already exists a common solution, UrlRewiteFilter. See a link here: http://wiki.apache.org/tomcat/AddOns Best regards, Konstantin Kolinko --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@tomcat.apache.org For additional commands, e-mail: users-h...@tomcat.apache.org
