browser caching policy

Hello,

That is a response for an image that was not processed after several tries and it is set to try at a much later date.
This can be resolved by making sure that your images are accessible, if you have any service that is blocking or limiting access to your website you should make sure to whitelist the User Agent: Optimole (1.0)

After that clear the cache from Optimole and the service will try again to process the images.

Let me know if this answers your question or if you have more, also if you can share with us a link to your website or image that is returning this response I can provide you with more information.

Thank you!

My concern is still the same.

302 status function is used for temporary redirect, now forcefully adding

cache-control: public, max-age=21576072 doesn’t make any sense.

It’s an alarming step that damage is PERMANENT for 21576072 seconds.

Even though origin end fixes something, what happened with 302 for a user is not going to fix ever for a long time. The 302 redirects will continue to follow for defined TTL.

I hope you get my concern. That is why I said, use no-cache for 302. The irony, if the goal is cached then simply use 301! if you want to damage more (Just saying!) ?? ??

Thanks

Your rival ShortPixel understand this thing, and they don’t do this silly stuff. They always avoid caching when doing temp redirect for processing.

See this https://i.imgur.com/RS9xyRg.png

The motivation is clear. If the origin end image becomes reachable at any point, they can put into the process and start serving from the CDN.

I hope this clarifies much better.

Hello,

Thank you for the feedback, I understand how this can cause issues now, I will take this to our development team and we will try to improve this in the future.

Let us know if you have more questions or feedback.
Thank you!