DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20919>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://nagoya.apache.org/bugzilla/show_bug.cgi?id=20919

"scheme" property or "secure" property in server.xml does not work for Coyote HTTP 
connector

           Summary: "scheme" property or "secure" property in server.xml
                    does not work for Coyote HTTP connector
           Product: Tomcat 4
           Version: 4.1.24
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Connector:Coyote HTTP/1.1
        AssignedTo: [EMAIL PROTECTED]
        ReportedBy: [EMAIL PROTECTED]


If I configure a Coyote HTTP/1.1 Connector using the connector class 
org.apache.coyote.tomcat4.CoyoteConnector and add the following properties to 
the connector configuration in server.xml

scheme="https" secure="true"

Calls to getScheme() and isSecure() do not return the expected values - 
specifically we get the values "http" and false returned.  Looking at the code, 
it appears that at no point does the default value get overridden.  According 
to the documentation, these parameters should be configurable for this 
connector.

Doing exactly the same thing using the Coyote JK connector (the protocol 
handler org.apache.jk.server.JkCoyoteHandler) does work correctly.

An example from server.xml that we have problems with is:

    <Connector className="org.apache.coyote.tomcat4.CoyoteConnector"
               port="30078" minProcessors="5" maxProcessors="75"
               enableLookups="true" redirectPort="8443"
               secure="true" schema="https"
               acceptCount="10" debug="0" connectionTimeout="20000"
               useURIValidationHack="false" />

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to