URL containing special characters

[bzwei]

Issue #183 and PR #184 seems not solving the issue with URL containing special characters. The encoding attempt only stops RestClient from complaining about the format of the URL, but the actual request using the encoded URL does not get back properly.

A further investigation may require a conversation with Microsoft concerning the format of URL if it contains special character (in the case of https://bugzilla.redhat.com/show_bug.cgi?id=1346034, { and }).

[bzwei]

@djberg96 Do you have a chance to escalate this question to Microsoft? The sample URL is https://sandboxrg4183.blob.core.windows.net/wahv19c04becbc71f39b18/copied-{05A9192A-07E7-467E-878E-660BF9F68A74}.vhd

[djberg96]

We should be able to simulate that by renaming one of our own private images. We can see what the CLI does, too.

[djberg96]

As discussed on skype, there are two places that need fixing. First, is the constructor for azure-signature, which I will update to automatically escape the first argument. The second will require an internal change in the azure-armrest gem when building headers.

[bzwei]

The fix by #184 is sufficient in azure-armrest.
ManageIQ/azure-signature#2 fixes azure-signature.