[rabbitmq-discuss] shovel auth change in 3.3.0?
michael.laing at nytimes.com
Mon Apr 7 12:16:23 BST 2014
Hmmm - yes that's a problem.
The amqp URI BNF in the rabbitmq docs includes this:
amqp_userinfo = username [ ":" password ]
> username = *( unreserved / pct-encoded / sub-delims )
> password = *( unreserved / pct-encoded / sub-delims )
which indicates that an empty password is acceptable in the URI,
Of course that doesn't mean the shovel has to accept it.
Possibly '1*' should be used instead of '*' above...?
It's a pretty small buglet in the scheme of things...
On Mon, Apr 7, 2014 at 6:47 AM, Simon MacMullen <simon at rabbitmq.com> wrote:
> On 04/04/2014 16:37, Laing, Michael wrote:
>> Here's an example - one shovel fails and the other works. The difference
>> is the colon which, strictly speaking, perhaps shouldn't have been there
>> - but used to work:
> Ah right, reproduced. The difference is in how URI parsing works - in
> 3.2.x, "amqp://user:@/vhost" would be treated as a direct connection with
> no password (i.e. assumed authenticated), while in 3.3.x it would be
> treated as a direct connection with a password of "".
> So it's probably a bug. I just can't decide if it's a bug in 3.2.x or
> Cheers, Simon
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the rabbitmq-discuss