Has anyone considered fixing the following Tomcat standalone issue: if a request is made to "www.xyz.com", tomcat auto redirects (per the welcome files list) to "www.xyz.com/index.html". That's a 302 http redirect. Aside from this being a very non-standard approach th handling default files within a directory, it is extremely problematic when dealing with Search Engines.
Search engines hate 302s and penalize most sites that utilize them, particularly as their default page. Further in the case of Google, a page rank is assigned to a url based upon inboind links. If the inboind links are all to "www.xyz.com" and that url is just a redirect, you will never benefit from the inbound links to your default url and never achieve a nigh ranking. For these reasons this "feature" of tomcat renders the standalone http server virtually commercially non-viable. This is a major concern for any commercial site that reaps traffic from search engines, or from inbound links. I setup my site using tomcat standalone because I saw no reason to set it up with Apache initially. But this one single reason is making me seriously second guess that choice. Is this not somehting that can be easily fixed in a future version? And if it can be fixed .... I would like to beg ... grovel ... anything ... to have this changed. Otherwise, re-setting up with apache is going to cost me a fair amount of $$$ and time at this point. :-\ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
