Reported on index_image_dfsmysql.php, but seems valid on all index_image_*.php files.
When a file on the NAS is missing (but the file reference exists in the DB) eZ returns a white/blank page. In the case of DFS, it goes like this:
When the file doesn't exist, the script just ends without serving anything.
This is an error situation, so an error message should be returned. This can improve error handling of proxies and load balancers. The customer wants a 5xx error. When the file doesn't exist in the database, 404 is returned. I'm not sure which is best.
- Delete an image file on the NAS, and in local storage
- Try to access that image