问题
We have been using ImageResizer serving images from disk for quite a while and it has been a great product for us!
Now we are trying to upgrade services to scale and using S3 for storage and running into a major issue for us.
If the image does not exist at S3 there is an AWSSDK error being thrown, that looks like is then preventing the image from ever being loaded through ImageResizer and continues to throw 404 even after the image has been loaded to S3.
To replicate the problem simply have S3Reader2 plugin running and try to pull up an image that does not exist in S3. Then load the image to S3 and it will not load the image unless you restart the application pool.
Info you likely want/need to help troubleshoot:
- ImageResizer diagnostic output
- The Exception being thrown when running in Visual Studio
Anyone else run into this? is there a workaround?
回答1:
You are using cacheMetadata="false", which is a v4+ configuration parameter.
You are using the v3.4.3 dlls. Upgrading to v4 should resolve the issue. v3 does not have a way to fully disable metadata caching (Sliding expiration defaults to 1 hour).
来源：https://stackoverflow.com/questions/30765665/imageresizer-s3reader2-plugin-404-error-after-image-has-been-uploaded