You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Martin Kleiman (JIRA)" <ji...@apache.org> on 2018/07/14 21:17:00 UTC
[jira] [Updated] (DISPATCH-1040) websocket listener doesn't work
with requireSsl, requireEncryption or EXTERNAL mechanism
[ https://issues.apache.org/jira/browse/DISPATCH-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Kleiman updated DISPATCH-1040:
-------------------------------------
Attachment: qdrouterd.tar.gz
qdrouterd.conf
a.py
I tried this with dispatcher but it won’t work either. Not sure if this is the same problem.
From core/transport.c in proton
if (transport->encryption_required && !pn_transport_is_encrypted(transport)) {
pn_do_error(transport, "amqp:connection:policy-error",
"Client connection unencrypted - forbidden@@@@@@@");
pn_set_error_layer(transport);
is where it errors off
Sent from Mail for Windows 10
> websocket listener doesn't work with requireSsl, requireEncryption or EXTERNAL mechanism
> ----------------------------------------------------------------------------------------
>
> Key: DISPATCH-1040
> URL: https://issues.apache.org/jira/browse/DISPATCH-1040
> Project: Qpid Dispatch
> Issue Type: Bug
> Reporter: Gordon Sim
> Priority: Major
> Attachments: a.py, qdrouterd.conf, qdrouterd.tar.gz
>
>
> If listener has httpe=true and requireSsl=true, then even if you connect with ssl, the connection is closed with an error form proton:
> amqp:connection:policy-error Client connection unencrypted - forbidden
> This is because proton does not know the connection is using ssl. This also prevents EXTERNAL being used.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@qpid.apache.org
For additional commands, e-mail: dev-help@qpid.apache.org