Your cdn should then only be associated with the blob account that contains your image cache container with your in-site request url getting redirected to something like.
So, after pointing my CDN to the cache blob container and changing the setting UseCachedContainerInUrl to true on the cache.config everything works as expected.
Thank you James for pointing me out on the right direction.
Azure Blob Cache 404 on remote processing
Hi
I'm making a demo using Slimsy and Azure Blob Cache, but when I try to do any image processing remotely I get a 404 error.
This is my cache.config file:
This is my security.config file:
The url I'm using to transform remotely: http://slimsydemo.azurewebsites.net/remote.axd/slimsydemocdn.azureedge.net/media/1004/people-q-c-640-480-7.jpg?width=200
And as you can see the image actually exists: http://slimsydemocdn.azureedge.net/media/1004/people-q-c-640-480-7.jpg
I already checked that my blob container is public.
Any ideas about what is missing?
Cheers.
Edit:
I'm using Umbraco 7.3.7, ImageProcessor 2.3.3, ImageProcessor.Web 4.5.3, ImageProcessor.Web.Config 2.2.5 and ImageProcessor.Web.Plugins.AzureBlobCache 1.0.8
Hi Cristhian,
So you're storing your media files in blob storage as well as the cached images?
If so what
IFileSystem
provider implementation are you using?James
Hey James,
No, I'm not storing the images in blob storage. I'm storing them on the site and using an Azure CDN.
If I understand correctly how the package works, when I go to a url like: http://slimsydemo.azurewebsites.net/media/1002/animals-q-c-640-480-2.jpg?width=100 it should redirect me to the cdn version of that image. Instead of doing that I get a 404. I checked the container and the images are there.
I know I'm missing something but I just don't see what it is.
The package should allow you to request a local media file as follows
This would then be processed and cached in blob storage. That works normally out of the box.
What I have noticed in your setup is that the successful request url
contains the relative path
media
and is pointed at a cdn.Though the url to your domain is
How have you managed that if your media folder is not stored in blob storage?
If you are using locally stored media the paths to your media files should be relative to your domain with no cdn involved.
e.g.
Your cdn should then only be associated with the blob account that contains your image cache container with your in-site request url getting redirected to something like.
(I plucked the hash out of thin air there. It's not representative of your real final url)
Something is definitely incorrect about the way you have set up your Azure account.
The CDN source is the website, that's why the urls are equivalent between the site and the CDN.
I'll try to point my CDN to the cache folder and see how it goes. If that doesn't work then I'll try to store all the media in blob storage.
So, after pointing my CDN to the cache blob container and changing the setting UseCachedContainerInUrl to true on the cache.config everything works as expected.
Thank you James for pointing me out on the right direction.
Ah excellent! So glad you got it worked out. :)
Could you mark one of the responses as an answer so we can close the thread.
Cheers!
is working on a reply...