[
https://issues.apache.org/jira/browse/QPID-3514?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13121121#comment-13121121
]
Zane Bitter commented on QPID-3514:
-----------------------------------
It's true that this is a rather tactical patch. The goal from the point of view
of the Matahari project was to come up with a patch that can be applied on top
of 0.12 in Fedora with minimal impact to existing users (i.e. not breaking any
ABIs, &c.).
Of course I'm more than happy to work with y'all to come up with a better
long-term solution for 0.14 and above, where I assume it's OK to change stuff
like the plugin interface. I agree with Andrew's comments about what that
should look like: accept the connection first and only decide on the type as
part of the handshake code.
> 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:[email protected]
