问题描述
我们一直在使用ImageResizer服务从磁盘映像相当长的一段时间，它一直是一个伟大的产品给我们！
We have been using ImageResizer serving images from disk for quite a while and it has been a great product for us!
现在，我们正在努力提升服务的比例，而使用S3存储和运行成为一个主要的问题对我们来说。
Now we are trying to upgrade services to scale and using S3 for storage and running into a major issue for us.
如果图像没有在S3中存在有一个AWSSDK错误被抛出，看起来像，然后$ P $从以往任何时候都正在通过ImageResizer加载并继续即使在已经加载到S3抛出404 pventing图像
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.
要复制的问题，只是有S3Reader2插件运行，并试图拉起来，不S3中存在的图像。然后加载图像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?
推荐答案
正在使用 cacheMetadata =假，这是一个V4 +配置参数。
You are using cacheMetadata="false", which is a v4+ configuration parameter.
您使用的是v3.4.3的DLL。升级到V4应该解决的问题。 v3中没有一个方法来完全禁用的元数据高速缓存（滑动期满默认为1小时）。
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).
这篇关于图像后ImageResizer S3Reader2插件404错误已经上传的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持！