Match pika implementation of URI parsing.

[bwarren2]

As detailed here, there is a difference in how this library and pika interpret the same URI. The pika solution seems cleaner, and I wanted to check for interest in my forming a pull request.

If the URI is

CLOUDAMQP_URL=amqp://guest:guest@localhost:5672/

and the connection is established with

factory.setUri(System.getenv("CLOUDAMQP_URL"));

As things stand, this results in a vhost of "" and a connection error in a default rabbitmq setup (which has a default vhost of /). Is there interest in a pull request to return a vhost of / instead of "", to make the default behavior match the default rabbitmq setup?

[michaelklishin]

This client is the reference implementation for RabbitMQ. Pika must much ours. Sorry.

[michaelklishin]

Note that this change has been discussed multiple times over the years. More often than not we come across clients that have issues around escaping and so on. FWIW we now have a URI parsing spec which is fairly sensible in my opinion. Small differences such as the one above are OK and I agree that Pika's approach is more beginner friendly. However, at this point it makes more sense for us to stick to the spec we have.

[bwarren2]

That makes sense. I didn't see an open or closed issue about this, so I thought it worth the ask. Thanks for the perspective!