tomcat-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Bill Barker" <>
Subject Re: cvs commit: jakarta-tomcat-connectors/util/java/org/apache/tomcat/util/http/mapper
Date Sat, 04 Jun 2005 19:27:13 GMT

----- Original Message ----- 
From: "Remy Maucherat" <>
To: "Tomcat Developers List" <>
Sent: Saturday, June 04, 2005 10:29 AM
Subject: Re: cvs commit: 

>Peter Rossbach wrote:
>> Hey Remy,
>> For usefull feature I don't give up :-)
>Fine, I'll just revert your patch then ;)
>> The default of host alias matching is off. The current implementation is 
>> little bit fast
>> then the old one. (Great) Every user of this feature can limit the 
>> dynamic host addition with
>> <Connector port="8080" allowedAliasMatches="10" />
>The issue is that this mechanism is bad, period.

I have to agree with Remy on this.  The issue is that the code is just plain 
bad :(.  So I'm going to add my -1 to the patch until the mechanism is 
cleaned up.  In fact, I'd have -1ed it just for the "import com.sun....." 
line alone.

>> The wild card alias usage is very useful for tomcat hoster. Now the 
>> customer can use
>> a new host subdomain without change the server.xml. Very nice and the 
>> admin must do nothing.
>And the usefulness of that is non existent as well. What's the purpose of 
>"adding" hosts if they are all the same ?
>> simple add first time <Alias>*</Alias>  to your host.
>> +1 vote for this feature.
>-1 vote for this feature.

This message is intended only for the use of the person(s) listed above as the intended recipient(s),
and may contain information that is PRIVILEGED and CONFIDENTIAL.  If you are not an intended
recipient, you may not read, copy, or distribute this message or any attachment. If you received
this communication in error, please notify us immediately by e-mail and then delete all copies
of this message and any attachments.

In addition you should be aware that ordinary (unencrypted) e-mail sent through the Internet
is not secure. Do not send confidential or sensitive information, such as social security
numbers, account numbers, personal identification numbers and passwords, to us via ordinary
(unencrypted) e-mail.

View raw message