[
https://issues.apache.org/jira/browse/QPID-5692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13968315#comment-13968315
]
Justin Ross commented on QPID-5692:
-----------------------------------
My mistake, I didn't set one up. I assumed it would use an unsafe devel cert
or fail (or warn) on start if SSL is not configured.
Maybe a warning plus a pointer to
http://wiki.eclipse.org/Jetty/Howto/Configure_SSL is in order. I checked the
latest trunk docs, and I don't believe they have any guidance about how to
setup HTTPS for admin.
Since I was in error, but there's still something to consider here, I'll recast
this as an RFI. Sorry for the misdirection.
> Issue a warning when web management is not SSL secured
> ------------------------------------------------------
>
> Key: QPID-5692
> URL: https://issues.apache.org/jira/browse/QPID-5692
> Project: Qpid
> Issue Type: Improvement
> Components: Java Broker
> Affects Versions: 0.29
> Environment: Fedora 19, x86-64, Java 1.7, Firefox 28, Chrome 34
> Reporter: Justin Ross
> Attachments: a.txt
>
>
> Plain HTTP works fine, but SSL fails. According to Firefox:
> {noformat}
> An error occurred during a connection to localhost:8080. SSL received a
> record that exceeded the maximum permissible length. (Error code:
> ssl_error_rx_record_too_long)
> {noformat}
> Chrome just reports an SSL protocol error.
--
This message was sent by Atlassian JIRA
(v6.2#6252)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@qpid.apache.org
For additional commands, e-mail: dev-h...@qpid.apache.org
