You are viewing a plain text version of this content. The canonical link for it is here.

Posted to bugs@httpd.apache.org by bu...@apache.org on 2002/11/20 11:14:56 UTC

DO NOT REPLY [Bug 14703] New: - unimplemented RFC2817 - upgrading to TLS within HTTP/1.1

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=14703>.
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=14703

unimplemented RFC2817 - upgrading to TLS within HTTP/1.1

           Summary: unimplemented RFC2817 - upgrading to TLS within HTTP/1.1
           Product: Apache httpd-2.0
           Version: 2.0.43
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Major
          Priority: Other
         Component: Core
        AssignedTo: bugs@httpd.apache.org
        ReportedBy: ased@cce.cz


It looks that there is missing functionality in HTTP implementation in Apache -
no support for RFC2817.
Although it seems that there is already some support for HTTP switching protocol
- eg. definition for HTTP_SWITCHING_PROTOCOL - as this was already defined in
old RFC2616 - Apache is based on that rfc.

Without RFC2817 features it is impossible to setup name based virtual hosting
with SSL/TLS enabled - highly required nowdays.

Suggestions or am I wrong?

---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org