> I've deployed an app using Tomcat Standalone (www.hotel.us) and while
there
> have been several issues that were a little less than obvious, I have
found
> a solution to every single one of them and am overall pretty satisfied
with
> tomcat. but this one little thing would force me to have to go to apache.
As has been said, try Matt Parker's patch. It should work the way that
Craig mentioned, and Tomcat 5 should also work that way from what I read.
> 1. A comparison was made - using tomcat as a web server is like racing a
mac
> truck.
Yeah, that'd be my stated opinion, and I'm sure that someone will disagree
with it. As far as I'm concerned, for many applications Tomcat Standalone
is like flying cotton canvas sails on a beautiful ACC sloop. Yeah, you'll
get somewhere, but I'll take Kevlar any time. Note that in this metaphor,
Tomcat is a beautiful ACC sloop (nicer imagery than a Mack truck), but the
built-in web server (cotton canvas) still isn't the equal of Apache
(Kevlar). If you want the most out of your boat, you equip it properly.
> If this sort of issue is defended by the community (302s etc)
> then there should be a blatant disclaimer when downloading
> the standalone that it is not intended for production use.
I have no idea whether the Tomcat developers actually consider the built-in
web server to be production quality or not. It really would depend upon
what you demanded of it. Personally, I'd never use it except for
prototyping. Even for a Web service server, I might want the load balancing
option provided by a front-end server. But, again, that's my personal
opinion. YMMV. And, once again, since you have a published fix for the
problem, I can't see that this is redirect v forward issue should continue
to be viewed as an issue.
--- Noel
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
