You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@qpid.apache.org by "Alan Conway (JIRA)" <ji...@apache.org> on 2018/10/02 13:55:00 UTC
[jira] [Updated] (PROTON-1946) [cpp] connection config file parser
mis-handling TLS defaults
[ https://issues.apache.org/jira/browse/PROTON-1946?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Alan Conway updated PROTON-1946:
--------------------------------
Description:
The C++ connection configuration parser mis-handles default values in several ways:
* tls is not enabled unless there is a tls: {} section - it should be enabled (with default config) if scheme: amqps is present even if there is no tls section
* in several cases an explicit 'field: null' is treated differently (as an error) from field being absent (use default value). null and absent should be equivalent.
* Host defaults to "", it should be "localhost"
* Some exceptions from jsoncpp are leaked, they should be wrapped in proton::error
* Need additional tests to cover all of the above
was:
The C++ connection configuration parser mis-handles default values in several ways:
* tls is not enabled unless there is a tls: {} section - it should be enabled (with default config) if scheme: amqps is present even if there is no tls section
* in several cases an explicit 'field: null' is treated differently (as an error) from field being absent (use default value). null and absent should be equivalent.
* Host defaults to "", it should be "localhost"
* Some exceptions from jsoncpp are leaked, they should be wrapped in proton::error
> [cpp] connection config file parser mis-handling TLS defaults
> -------------------------------------------------------------
>
> Key: PROTON-1946
> URL: https://issues.apache.org/jira/browse/PROTON-1946
> Project: Qpid Proton
> Issue Type: Bug
> Components: cpp-binding
> Affects Versions: proton-c-0.25.0
> Reporter: Alan Conway
> Assignee: Alan Conway
> Priority: Major
> Fix For: proton-c-0.26.0
>
>
> The C++ connection configuration parser mis-handles default values in several ways:
> * tls is not enabled unless there is a tls: {} section - it should be enabled (with default config) if scheme: amqps is present even if there is no tls section
> * in several cases an explicit 'field: null' is treated differently (as an error) from field being absent (use default value). null and absent should be equivalent.
> * Host defaults to "", it should be "localhost"
> * Some exceptions from jsoncpp are leaked, they should be wrapped in proton::error
> * Need additional tests to cover all of the above
--
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