You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Zane Bitter (Updated) (JIRA)" <ji...@apache.org> on 2011/09/29 16:18:46 UTC
[jira] [Updated] (QPID-3514) Allow SSL and non-SSL connections on
the same port
[ https://issues.apache.org/jira/browse/QPID-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Zane Bitter updated QPID-3514:
------------------------------
Attachment: ssl-mux.patch
The attached patch implements this when the SSL Plugin is enabled and both AMQP and AMQPS are configured to use the same port (i.e. port == ssl-port).
> Allow SSL and non-SSL connections on the same port
> --------------------------------------------------
>
> Key: QPID-3514
> URL: https://issues.apache.org/jira/browse/QPID-3514
> Project: Qpid
> Issue Type: Improvement
> Components: C++ Broker
> Affects Versions: 0.12
> Reporter: Zane Bitter
> Attachments: ssl-mux.patch
>
>
> The Matahari Project (http:://matahariproject.org for the uninitiated) has run into an issue with our use of Qpid in that IANA policy is now to refuse to assign separate TCP ports for SSL/TLS-wrapped versions of protocols, which leaves us with only a single port assigned to Matahari.
> We would like to be able to accept both SSL and non-SSL connections on the same port.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
Apache Qpid - AMQP Messaging Implementation
Project: http://qpid.apache.org
Use/Interact: mailto:dev-subscribe@qpid.apache.org