[
https://issues.apache.org/jira/browse/PROTON-725?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14182596#comment-14182596
]
Dominic Evans commented on PROTON-725:
--------------------------------------
[~E528527] this is what URL encoding was designed for? :) You should replace
any reserved characters in the password before using it in the amqp:// URL
See http://en.wikipedia.org/wiki/Percent-encoding
%2F would replace the / in your password
> pni_parse_url does not properly handle Base64 in URL
> ----------------------------------------------------
>
> Key: PROTON-725
> URL: https://issues.apache.org/jira/browse/PROTON-725
> Project: Qpid Proton
> Issue Type: Bug
> Components: proton-c
> Affects Versions: 0.8
> Reporter: German Shepherd
> Priority: Minor
>
> Our provisioning system provides us with a password in Base64 format, which
> can actually contain a slash character(s): '/'
> This breaks the ability of {{pni_parse_url()}} to handle such URLs.
> Example of URL string on which the parsing fails:
> {{amqps://0ABCDEF1:/ExlxtfN+UxfExRxuwxIeFxeFzXLxxg+fxPx3x8xxU=@myself.servicebus.windows.net/out/txxxx/Subscriptions/syyyy}}
> Instead of filling up the "user" and "password" variables, it puts the actual
> contents to "host" and "port".
> With the actual code it is a correct behavior - and *it is* also mentioned in
> the comment right in front of the pni_parse_url() function.
> Yet I would need an update to the functionality, to handle the Base64 in
> password properly (anyone on Azure platform might run to this issue, soon or
> later).
> Note. I'm running the SVN rev 1633464 (latest trunk of 10/23/2014) version of
> ProtonC (C / Linux).
> Thanks for looking at this.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
