problem listing blobs with reserved url characters about azure-storage-cpp

[JasonYang-MSFT]

@shlomiapel
# is the fragment identifier in url, which lead your blob name into two parts, path and fragment.
You could try to encode uri with specifying the field.
try this to encode uri:

web::uri::encode_uri(blobName, web::uri::components::path)

A better way to get blob referencing is:
container.get_blob_reference(blobName);
Or if you are trying to use block blob:
container.get_block_blob_reference(blobName);

[shlomiapel]

i have already tried to encode the blob name using all component types and none work.
in addition the list fails to find the blob since there is an exception in case the blob name is not encoded and if encoded, the blob is not found.

[shlomiapel]

i have switched to getting the blob reference through the container and not the uri and i succeed to create a blob with the correct name but now fail to list or delete it. in both cases i get an exception caused by authentication mismatch. even if i encode the name. if i encode using encode_data_string, there is no exception but the blob is not found.
BTW, deleting the created blob is now possible only through the azure explorer. it fails in the Azure web UI as well.

[JasonYang-MSFT]

@shlomiapel
There is a bug found in authentication while blob name contains '&'. Will send a fix in PR ASAP. Then you can merge the fix and build the sdk from source code accordingly.

BTW, the blob name seem so different to other customer. Would you like to share your scenario with us? It will be much grateful if you can send me email for a brief introduction if you want. That will help us a lot.

[JasonYang-MSFT]

@shlomiapel
PR #85 send to fix authentication fail for blob names contain '&'.

[shlomiapel]

Thank you for the prompt update. what about using the class to refer to blobs which contain special characters in their name? i.e. using the Ctor:
WASTORAGE_API cloud_blob(storage_uri uri, storage_credentials credentials);

[shlomiapel]

regarding blob naming methodology, we create blob names which include names of VMs in our setup.
This bug happened when testing VMs with special characters in their name. This can happen in a real customer setup where they have a VM names "Finance & IT" for example or "ITServer#3", etc...

[JasonYang-MSFT]

@shlomiapel
Thanks for your contribution.
We have released 2.4.0, this bug is fixed in this release. You can try our newest release if you want.