Take the tour ×

I have set a 'public' container where the blobs are stored as 'private', however irrespective of that I am still able to access the blobs directly with their URL within the container.

Any idea of why this is happening?


share|improve this question
For questions like these, it really helps if you include a code snippet. –  David Makogon Mar 8 at 21:45
Hi David, when you go into your container, you will see there is a blob URL. The thing is you can access the private blob directly as long as you know the url. –  bobo2000 Mar 8 at 21:49
I understand what you're saying. But without showing code for how you set up permissions for container and blob, there's absolutely no chance of someone diagnosing this without a lucky guess. –  David Makogon Mar 8 at 21:58
@bobo2000, that information is not correct. If the blob container is marked as private then you cannot access the blobs inside regardless of if you know the URL or not. –  kwill Mar 8 at 22:04
kwill was spot on, thanks guys. –  bobo2000 Mar 8 at 22:10
add comment

1 Answer

up vote 2 down vote accepted

I suspect that your browser or some other cache server is caching the file and you are not actually going to blob storage to get the file. You can use Fiddler or Netmon to validate what requests are being made to storage, or perhaps try a different machine or an in-private browsing session.

Once a blob container is marked private you cannot access any blob in that container without the private key or a signed request.

share|improve this answer
Yep, it turns out my chrome was caching the file without realising. –  bobo2000 Mar 8 at 22:09
add comment

Your Answer


