>I think Rashmi and I mean the same thing by "translation" and "resolution". >Yes, the browser does the URL resolution, and if you have relative >URLs then the trailing slash is meaningful. If you remove it you will >change the meaning of relative URLs on that page. >Len
On 1/17/07, lightbulb432 <[EMAIL PROTECTED]> wrote: > > I want to get rid of the trailing slash for style issues (really a small > concern) and also to learn about customization within Tomcat as well as URL > rewriting. I think the benefits of keeping the trailing slash far outweight the benefits (if any) of removing it. If you want Apache's features with Tomcat, you might already know about Connectors, with them you can connect Tomcat to Apache, and make use of Apache's capabilities along with Tomcat. Here are the benefits: http://tomcat.apache.org/faq/connectors.html#integrate URL rewriting is very useful, if you are aiming at making URLs search engine friendly, you can make dynamic URLs appear as if they are static to both search engines and users. > > Regarding URL rewriting, did you mean the following? > > <rule> > <note>Testing trailing slash.</note> > <from>(.*)/</from> > <to>$1</to> > </rule> > > Perhaps that works rather than a <to> value of (.*) Sorry, my mistake. The above syntax is correct (not the one I gave previously). Although the above syntax is correct it still doesn't work when I tried it, it simply tried to show the directory listing instead of rendering the page at the directory. > > Are you sure about what you said: "URL Rewriting will not help in > eliminating the trailing slash because it's the browser that does the URL > translation." The way I interpreted Len's comments were that it's the server > that does the URL creation/translation, and the browser that does URL > resolution...two different concepts... > There is some long discussion along the same lines http://lists.samba.org/archive/jcifs/2004-December/004395.html > > Rashmi Rubdi wrote: > > > > Could you explain to us, why you want to get rid of the trailing slash ? > > > > > >>Could anyone please expand a little more on what's meant by the two > >>statements below? > > > >>>Len Popp wrote: > >>> > >>> It doesn't matter if it's done by URLRewriteFilter or some other > >>> method because it's the browser that interprets the relative URLs, not > >>> the server. > >>> > > > > URLRewriteFilter is an application that allows you to rewrite URLs, that > > means, for example if you have a URL like > > http://localhost:8080/page.jsp?param1=499¶m2=333 , with URL > > rewriting you can represent it anyway you want with a regular expession > > pattern > > that means you can represent it like this > > > > http://localhost:8080/page/499/333/ , or any other pattern. > > > > > > But what Len is saying (and I verified that he's right), is that URL > > Rewriting will not help in eliminating the trailing slash because it's the > > browser that does the URL translation. > > > > I tried URL rewriting with this pattern to test your case: > > <rule> > > <note>Testing trailing slash.</note> > > <from>(.*)/</from> > > <to>(.*)</to> > > </rule> > > > > When I tried http://localhost:8080 , instead of http://localhost:8080/ > > it didn't work, just showed a blank screen. > > > > I had to delete the URL rewriting rule, only after that it worked. > > > >> If the containing page's URL looks like a file when it's > >> really a directory, the browser will get them wrong. > >> ____________________________________________________________________________________ Don't get soaked. Take a quick peak at the forecast with the Yahoo! Search weather shortcut. http://tools.search.yahoo.com/shortcuts/#loc_weather --------------------------------------------------------------------- To start a new topic, e-mail: users@tomcat.apache.org To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
