You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tomcat.apache.org by bu...@apache.org on 2008/01/28 15:42:32 UTC
DO NOT REPLY [Bug 44309] - Possible overriding the security state of the connection
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG�
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=44309>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND�
INSERTED IN THE BUG DATABASE.
http://issues.apache.org/bugzilla/show_bug.cgi?id=44309
------- Additional Comments From robert.kovacs@siemens.com 2008-01-28 06:42 -------
Detailed feature request:
It would be great if TomCat could offer an interface to influence the decision
whether the connection is secured or not in case of isSecure() and scheme() methods.
Therefore the actual decision based on the connector configuration could be
redefined with our own implementation.
The interface could contain a method with an input parameter with type
java.net.Socket which belongs to the actual connection and it could return
boolean value indicating that the underlying layer is secured or not based on
the socket parameter.
For example:
package org.apache.coyote;
public interface SecurityExtension {
public boolean isSecure( java.net.Socket socket )
throws Exception;
}
Similar to protocol attribute of connectors the implementation class of this
interface could be specified as an optional connector attribute.
The interface method could be invoked in prepareRequest() method of
org.apache.coyote.http11.Http11Processor.java where the request scheme attribute
can be overridden.
--
Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org