Missing images should return 404 error

[tzyganu]

When editing a product in the backend, if one of the product images is missing I still get a 200 response.
If I take a look at the url I see an error message

Fatal error: Cannot instantiate interface Magento\Framework\App\Config\Scope\ReaderPoolInterface in

Missing images should give back a 404 response without going through the application.

[robfico]

See this Stack Exchange post for more info on how this works:
http://magento.stackexchange.com/questions/48894/missing-css-and-js-files-in-magento2-git-repository?atw=1

[antonmakarenko]

This problem has 2 solutions:

1. Fix the root cause (the fatal error) -- we'll try to reproduce this test case.
2. Make PHP show HTTP code other than 200 on fatal error. Here is an example how it can be done: http://stackoverflow.com/questions/13644550/http-status-header-on-php-fatal-error-code-proposition

[tzyganu]

@robfico I know how it works...I'm the one that actually wrote the answer you referred 😄

@antonmakarenko. The problem in this case is not the fatal error. The problem is that when an image is missing the application is instantiated. It should be a simple 404.

[antonkril]

@robfico I know how it works...I'm the one that actually wrote the answer you referred

Marius in action :)

[robfico]

LOL. Completely missed that. My original comment was I thought the RewriteRule was missing to exclude pub/media, but then I saw your post on SE. Yes, I agree, these should be simple 404s, instead of invoking Magento each time - costly and can easily cause issues with many 404s being hit.

[buskamuza]

@tzyganu,

he problem is that when an image is missing the application is instantiated. It should be a simple 404

In order to know if the image really exists, some part of the application is needed - in order to go through modules and themes and search for the file (according to the Magento inheritance rules).

In case "production" mode is enabled, it just returns 404 if the image is absent (or at least it should).

[otoolec]

@tzyganu does the response from @buskamuza resolve this issue for you? If you enable production mode then you should see a 404 error without the application being launched.

Can you confirm that this is the behavior you are seeing and close the issue? If you disagree, can you provide more information on what you would like to see changed?

[tzyganu]

@otoolec @buskamuza It seams to be ok now. On beta 2 I get the correct 404 message even if I'm on the developer mode. I don't know if this was an intentional fix or a side effect for something else. But that's not important. Thanks for it.