Actually, I found the archives by doing a google web search. In the thread it *sounds* like it has been added to Tomcat 5.0 and is not something I can toggle within the web.xml file. Is there any documentation on this? What precisely do I change within the web.xml file to get this behavior?
In the meantime I suppose I'll download tomcat 5.0 and play around to see if its something I can figure out. Thanks Neal -----Original Message----- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 16, 2003 10:58 AM To: Tomcat Developers List Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue Actually, How can I check the archives of this list? I did a search for the thread on google groups and nothing was found. I looked for the archives on apache.org but it looks like archives haven't been kept since then end of 2001. :( Thanks Neal -----Original Message----- From: neal [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 16, 2003 10:54 AM To: Tomcat Developers List Subject: RE: Request to Fix Tomcat Standalone 302 redirect Issue Aha! That's exactly what I was looking for - a forward rather than a redirect! Great, I will check out the thread and keep my fingers crossed that this is an optional behavior in Tomcat 5. As for the status, might I suggest that so long as this behavior is not changed and not optional that it should be well documented. This can be a serious caveat ... and a quite unexpected one. The documentation for Tomcat standalone gives no indication that it is inferior or that it implements an alternative standard due to the existance of apache. But if that's the case it should be noted as a guide for people new to the product who need to make informed decisions. Thanks. Neal -----Original Message----- From: Reinhard Moosauer [mailto:[EMAIL PROTECTED]] Sent: Sunday, February 16, 2003 4:47 AM To: Tomcat Developers List Subject: Re: Request to Fix Tomcat Standalone 302 redirect Issue Hi, at Jan 03, 2003 Matt Parker published a patch in this list: "[PATCH] forward instead of redirect for welcome files" which was discussed thourougly with Costin, Remy and others. I'm not sure about the conclusion of this. But it seemed that 5.0 should reintroduce this behavior by option. Please read that thread. Maybe there are some hints to get further. (I am also very interested in this changing this, but as long as apache ist an option, the priority stays medium...) Kind regards, Reinhard Am Sonntag, 16. Februar 2003 00:41 schrieb neal: > 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] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
