GeoCachorros

Hi nykkole, Thanks for your answer. You are right that most puzzles are broken because the third-party's response depends on some client request's characteristic (that it is not getting now to it thru imgproxy), but this is not my case. And you are right that you are not expressly caching, but the effect is the same. My website returns HTTP header "Pragma: no-cache", but imgproxy is stripping it and returning instead to the client "cache-control: public, max-age=31536000". The effect is that the browser is reusing its cached (incorrect version) copy of the image instead of retrieving every time the new (correct version) from my server (thru imgproxy). imgproxy should respect HTTP headers returned by the third-party site (at least those related to caching).

Hi nykkole. I think Groundspeak is mixing two different issues: proxying the images and caching them. I can understand Groundspeak wants now to proxy all images hosted on 3rd party sites in order to avoid 3rd party sites setting cookies at the client thru cache listings, but that doesn't necessarily mean you have to cache them. In fact, caching them makes many puzzles break: those that rely on returning on-the-fly a different image depending on some circumstances (e.g., some property of the client's request like the preferred language in the client's browser, some external circumstances retrieved by the 3rd party site...). In fact, I have noticed your imgproxy server is indeed ignoring the no-cache / Expires HTTP headers returned by the 3rd party site. Could you at least honor these headers?

I wonder how on Earth this change could ever be approved in the first time at HQ, as It was easily foreseeable that this would break many mysteries, e.g. those that rely on returning on-the-fly an image, maybe depending on the client's request... Some of our puzzles are broken, some by fellow geocachers, some we have solved in the past... Groundspeak please: - roll back this unfortunate change ("We have rolled this update back"; no, it's still on) - refrain in the future to change a service we are paying for without prior notice. Thanks.

>>>> the images were routed through a proxy server I wonder how on Earth this change could ever be approved in the first time at HQ, as It was easily foreseeable that this would break many mysteries, e.g. those that rely on returning on-the-fly an image, maybe depending on the client's request... Some of our puzzles are broken, some by fellow geocachers, some we have solved in the past... Groundspeak please: - roll back this unfortunate change ("We have rolled this update back"; no, it's still on) - refrain in the future to change a service we are paying for without prior notice. Thanks.