Closed Image proxy always returns status code 200

Kirby

Well-known member
Licensed customer
Affected version
2.2.15
No matter if an image exists or not and if the hash (if required) is correct or not - the image proxy always returns status 200.

This is IMHO semantically wrong and Google seems to consider such URLs as "soft 404".

Suggested Change
Return 404 if no image exists (or 410 it it existed in the past but was pruned)
Return 400 (or 403) if a required hash is missing or wrong
 
Automated triage: Design issue

Thank you for reporting this issue. When the image proxy can't serve an image (it is missing, the fetch failed, or the hash is wrong), it sends a placeholder 'missing image' picture. The failure is flagged in a response header and the response is marked not to be cached, but the status code stays 200. Returning an error status instead would be a change to how the proxy is designed rather than a bug fix.

This is an automated assessment. A member of staff may review and update it.
 
Back
Top Bottom