I stumbled on a possible issue when trying to get Azure Blob Storage for Media working.
I was getting the classic "image stored in Azure but serving only the original when a crop is requested". I then re-installed using package manager (previously by Nuget) to make certain that all my settings were correct.
At this point the crop urls stopped returning the originals and started erroring out with a "file too large" message.
I then tried a smaller image and all worked well. (I think, still no /cache appearing in the container.)
I have always recommended that clients use the largest/best image possible and returned crops. This somewhat future-proofs the system in case we ever need larger crops.
My questions: Can I change the filesize limits? Should I? If so, where?
Max image size with Azure Blob Storage for Media
I stumbled on a possible issue when trying to get Azure Blob Storage for Media working.
I was getting the classic "image stored in Azure but serving only the original when a crop is requested". I then re-installed using package manager (previously by Nuget) to make certain that all my settings were correct.
At this point the crop urls stopped returning the originals and started erroring out with a "file too large" message.
I then tried a smaller image and all worked well. (I think, still no /cache appearing in the container.)
I have always recommended that clients use the largest/best image possible and returned crops. This somewhat future-proofs the system in case we ever need larger crops.
My questions: Can I change the filesize limits? Should I? If so, where?
Hi Ault,
There are several areas to change it, but an important one is in the ImageProcessor Security.Config file as well as the areas in web.config.
Nik
is working on a reply...