Support Cross Origin Resource Sharing (CORS) via Access-Control-Allow-Origin header
http://en.wikipedia.org/wiki/Cross-origin_resource_sharing
This feature has many useful applications:
* loading of JSON data without JSONP wrappers
* pre-loading Image data with progress information
* pre-loading Audio data on browsers that otherwise suppress audio preloading
Christopher Currie
shared this idea
We will be supporting CORS soon for blobs, tables and queues.
17 comments
-
Danigosa
commented
How soon... it's pettry basic feature :S
-
Anonymous
commented
Just to reiterate the Access-Control-Allow-Origin header is required for WebGL textures, Canvas images - if you want to compsite, Webfonts, AJAX, WebAudio, HTML5 Video (when used as a texture) etc
-
Sav
commented
I've noticed that the March release implemented some CORS support. I haven't read anywhere that this includes Blob Storage support, so is it safe to assume that this feature is still coming? Or has it already been released, and I just haven't found the documentation yet?
-
Sergey Savchuk commented
That would be really great!!!
I'm currently implementing web access to azure storage.
Have to use intermediate proxy that supports CORS... -
Louis
commented
I need this too.
-
PulsarBlow
commented
Hello, does "soon" mean weeks or months ?
Almost 1 year we are waiting for this feature ! -
Nir
commented
Is there an ETA for this? We need to know whether we should start using different storage server, or wait for this to be completed on AZURE.
-
maarten.balliauw
commented
Will this be enabled on Access Control as well? (when using the OAuth endpoint from a SPA)
-
Anonymous
commented
I hope it is very soon, Scott!
-
Martin Svensson
commented
this is a great feature for chunk uploading of large files as well
-
Anonymous
commented
Not having this forces us to have our blob storage elsewhere so that our web app (MVC4) hosted in Azure can then download media files async. It crazy that while there is blob storage, we really can't use it for our web app until this is supported. #FAIL
-
Anonymous commented
This is also preventing the usage of web fonts in Firefox and IE, as they require the "Access-Control-Allow-Origin" header to render cross domain. Please allow us to add this header to our files. Its absence forces some very inconvenient workarounds (like storing files elsewhere). Both Amazon and Google support this.
-
Satish
commented
Recently Amazon announced CORS support in Amazon S3.
-
Andy B commented
Would be useful for javascript access to Table Storage since Shared Access Signatures were added in 2012-02-12 release.
-
Ben Goh commented
Yep, CORS is crucial for the proper functioning of our web game, there's currently no way of polling the queue from JavaScript other than going through a web role. That can scale, but it comes at a much higher cost than polling the game queue directly.
Please add this, Microsoft. Your Azure service is just 99% awesome without this bit. Thanks in advance! :-)
-
PulsarBlow
commented
This is needed on ACS endpoints too.
-
Jamison Morrow
commented
This is currently forcing us to use Google storage for web fonts (because they support the header). Why can we add all manner of custom metadata to our blobs, control content type, encoding, etc... but not dictate which origin domains can access it?
