Skip to main content

Shared Access Signature and URL encoding on Windows Azure

Playing a little with Shared Access Signature was quite nice. In this moment this new functionality has a great potential. Playing a little with it I found an odd bug that I introduce from the code. From the start you need to know that this bug was generated by me and the cause of it was not Windows Azure.
Normally after we generate the access signature we are adding it to the URL that we want to access and we get a code similar to this:
var accessSignature = myTable.GetSharedAccessSignature(…);
string accessURL = tableAccessURL + … + accessSignature;
Uri accessUri = new Uri(accessURL);
string myAccessLink = accessUri.ToString();
The only problem here is that the accessSignature can contains specials characters like ‘=’ or ‘+’. This kind of characters needs to be encoded in the URL. Because of this from time to time we will get an URL that is not valid. In my case last time I got an access signature that contained this kind of specials characters for 4 times in a row. Because of this we cannot accept this kind of solutions.
A better way to get the string of an Uri object is to use AbsoluteUri for example. Or any other method that know to encode the URL characters. Using this method we will not need to worry about encoding problems. The code should look like this:
var accessSignature = myTable.GetSharedAccessSignature(…);
string accessURL = tableAccessURL + … + accessSignature;
Uri accessUri = new Uri(accessURL);
string myAccessLink = accessUri.AbsoluteUri();
Another solution for our problem is to use “EscapeUriString” method of the uri. This will do the same think for us.
In conclusion we should be carefully about how we convert any kind of Uri to a string and know very well what kind of characters can appear in it. If the URL that is generated doesn’t need to be read by a user I will also try to escape the uri string using any solutions that is available.

Comments

Popular posts from this blog

How to audit an Azure Cosmos DB

In this post, we will talk about how we can audit an Azure Cosmos DB database. Before jumping into the problem let us define the business requirement: As an Administrator I want to be able to audit all changes that were done to specific collection inside my Azure Cosmos DB. The requirement is simple, but can be a little tricky to implement fully. First of all when you are using Azure Cosmos DB or any other storage solution there are 99% odds that you’ll have more than one system that writes data to it. This means that you have or not have control on the systems that are doing any create/update/delete operations. Solution 1: Diagnostic Logs Cosmos DB allows us activate diagnostics logs and stream the output a storage account for achieving to other systems like Event Hub or Log Analytics. This would allow us to have information related to who, when, what, response code and how the access operation to our Cosmos DB was done. Beside this there is a field that specifies what was th...

Why Database Modernization Matters for AI

  When companies transition to the cloud, they typically begin with applications and virtual machines, which is often the easier part of the process. The actual complexity arises later when databases are moved. To save time and effort, cloud adoption is more of a cloud migration in an IaaS manner, fulfilling current, but not future needs. Even organisations that are already in the cloud find that their databases, although “migrated,” are not genuinely modernised. This disparity becomes particularly evident when they begin to explore AI technologies. Understanding Modernisation Beyond Migration Database modernisation is distinct from merely relocating an outdated database to Azure. It's about making your data layer ready for future needs, like automation, real-time analytics, and AI capabilities. AI needs high throughput, which can be achieved using native DB cloud capabilities. When your database runs in a traditional setup (even hosted in the cloud), in that case, you will enc...

Cloud Myths: Migrating to the cloud is quick and easy (Pill 2 of 5 / Cloud Pills)

The idea that migration to the cloud is simple, straightforward and rapid is a wrong assumption. It’s a common misconception of business stakeholders that generates delays, budget overruns and technical dept. A migration requires laborious planning, technical expertise and a rigorous process.  Migrations, especially cloud migrations, are not one-size-fits-all journeys. One of the most critical steps is under evaluation, under budget and under consideration. The evaluation phase, where existing infrastructure, applications, database, network and the end-to-end estate are evaluated and mapped to a cloud strategy, is crucial to ensure the success of cloud migration. Additional factors such as security, compliance, and system dependencies increase the complexity of cloud migration.  A misconception regarding lift-and-shits is that they are fast and cheap. Moving applications to the cloud without changes does not provide the capability to optimise costs and performance, leading to ...