Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Message-ID: <13102190.1156462752785.JavaMail.jira@brutus>
Date: Thu, 24 Aug 2006 16:39:12 -0700 (PDT)
From: "Bill Stoddard (JIRA)" <dev@geronimo.apache.org>
To: dev@geronimo.apache.org
Subject: [jira] Commented: (GERONIMO-2348) Tomcat ConnectorGBean does not
 handle attribute values properly
In-Reply-To: <1343357.1156402090061.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit

    [ http://issues.apache.org/jira/browse/GERONIMO-2348?page=comments#action_12430340 ] 
            
Bill Stoddard commented on GERONIMO-2348:
-----------------------------------------

Why is the patch to http11protocol required?   The code being patched in tomcat simply sets the default values for these attributes; is the original (unpatched) code actually causing a problem?  I would be concerned if that's the case because I believe tomcat (w/o Apache Geronimo) allows these values to be overridden (user configurable) and tomcat does not have a problem with the defaults being set.  This part of the patch just doesn't seem right to me.


> Tomcat ConnectorGBean does not handle attribute values properly
> ---------------------------------------------------------------
>
>                 Key: GERONIMO-2348
>                 URL: http://issues.apache.org/jira/browse/GERONIMO-2348
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: Tomcat
>    Affects Versions: 1.0, 1.1, 1.1.1
>         Environment: Win XP, Geronimo Tomcat 1.1.1-SNAPSHOT
>            Reporter: Vamsavardhana Reddy
>         Assigned To: Vamsavardhana Reddy
>             Fix For: 1.1.2, 1.1.x, 1.2
>
>         Attachments: GERONIMO-2348.patch, http11protocol.patch
>
>
> Tomcat ConnectorGBean does not handle the following attributes properly.
>   1.  hostLookupEnabled
>   2.  redirectPort
>   3.  maxSavePostSize
>   4.  useBodyEncodingForURI
> There may be other attributes that are not handled properly as well.  So, far I have confirmed the above list.  I will continue investigation and update the list.
> A similar problem GERONIMO-2343 is observed and fixed by Krishnakumar B.  And the fix is also similar.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira