Support Cross Origin Resource Sharing (CORS) via Access-Control-Allow-Origin header
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
Thanks for submitting the request. We have released CORS and more today and details can be found at @ http://blogs.msdn.com/b/windowsazurestorage/archive/2013/11/27/windows-azure-storage-release-introducing-cors-json-minute-metrics-and-more.aspx
Ben Adams commented
Sure your CDN isn't cached on the CDN? We have been using the CDN for CORS for about 2 years (but not via storage)
Actually, its still not working for Azure CDN endpoints.
Marco Kroonwijk commented
Can you confirm (or deny) that CORS will be supported for the WAAD authentication endpoints as well? It's more like one and the same thing for all services isn't it? Or is there a reason to discriminate between Azure services getting CORS supports or not?
Looks like this blog post says it'll be the Holidays. I'm sorry.
"By end of CY ’13, we are targeting to release the following features:
•Secondary read-only access: we will provide a secondary endpoint that can be utilized to read an eventually consistent copy of your geo-replicated data. In addition, we will provide an API to retrieve the current replication lag for your storage account. Applications will be able to access the secondary endpoint as another source for computing over the accounts data as well as a fallback option if primary is not available.
•Windows Azure Import/Export: we will preview a new service that allows customers to ship terabytes of data in/out of Windows Azure Blobs by shipping disks.
•Real-Time Metrics: we will provide in near real-time per minute aggregates of storage metrics for Blobs, Tables and Queues. These metrics will provide more granular information about your service, which hourly metrics tends to smoothen out.
Anton Paisov commented
Valerii Shypunov commented
+1 - this is really needed
We've moved into "a few months" now.
Why's this taking so long? I built a bespoke implementation of the CORS protocol into our WCF services in a day to support x-origin requests. Pull finger.
Ted van der Veen commented
This is getting a bit frustrating.... We have solutions lined up for our customers that depend on this functionality to be deployed. Even in 'Preview' state would be fine for now.
We can bypass CORS issues in Chome while in development using http://stackoverflow.com/questions/3102819/chrome-disable-same-origin-policy but need to tell our customers when we can deploy this to the general public.
Can you please confirm a solid ETA??
Hey guys, is it possible to get an update on where this is at?
Jeroen Landheer commented
Feb 4: "We will have this soon!", 4 months later on Jun 4: "Within a few weeks!", It's August 2013 and still nothing. "Soon" isn't 6 months and "a few weeks" is a lot less than 2 months. If I would do this with my clients I'd be out of business. What's the ETA?
Are six weeks considered "a few"..?
If indeed it is expected "this fall", be Sep ot Nov, please say so.
Until we have CORS support, we have to either proxy all our images through our web server, or move them to Google Cloud / AWS. A real date would sure help...
If not already done, it would be helpful if this were true for WAAD authentication endpoints as well.
Nicholas Petersen commented
Eagerly awaiting this!
@Luiz: "Jai Haridas said it will come in fall":
That would be in the comments here: http://blogs.msdn.com/b/windowsazurestorage/archive/2013/07/12/introducing-storage-client-library-2-1-rc-for-net-and-windows-phone-8.aspx
This Fall? I was sure hoping for "in a few weeks"!
Luiz bicalho commented
Jai Haridas said it will come in fall
Luiz bicalho commented
In the build Jai Haridas said this is coming in the end of the year, is that correct?
Martin Svensson commented
This is great news!
Guthrie said today in this tweet: https://twitter.com/scottgu/status/341780823390957568 "we’ll have CORS support with storage in a few weeks - stay tuned"
There's been a big update today and still no CORS support. Are we looking at a 1, 6 or 12 month wait? At the moment I'm being forced to waste money implementing alternative solutions with competitors.