-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cache issue and 404's #57
Comments
Yeah, seems likely the extra characters in the file name would be the cause. I saw that happen once in one of my deployments, but it was over a year (and a couple of release versions) ago and only happened once. I don't remember identifying the cause, so it could still be there. Just looking at the code now, I see a potential bug in that the string for the hash should be null terminated and isn't. I'll push an update to that in a bit. Would you be able to try out a CI build when I have it ready to see if that fixes it up? |
I pushed a fix up if you want to give it a try. You'll need both the MagicScaler and WebRSize packages from CI |
New release is up that should fix this. |
Occasionally we're seeing 404s returned on all or nearly all image requests. These images should already be in the disk cache. If I delete the cache folders the images will appear once and then return to 404's for the next request. I'm guessing we might have some config issues. We are currently using option 2 where we register the module explicitly in the system.webServer section of the web.config.
One side note - the cached image files are all named like 3YR3JXXCᨾ跑�.IMG_1481.600x450.JPG is that an expected character set for naming strategy? I'm not sure if that is related to the 404s, but figured I would mention that.
Thanks!
The text was updated successfully, but these errors were encountered: