For some reason Laravel seems to be manipulating the response headers \'Cache-Control\' on the very last moment. I want to make browser caching possible.
class T
Although I do not know your exact configuration, I would assume that this is due to your Apache configuration, as header values can be overwritten there.
Have a look through all Apache configuration files and look out for lines starting with Header Set Cache-Control
, e.g. Header Set Cache-Control "no-store, no-cache, must-revalidate, post-check=0, pre-check=0"
Probably such a directive is set to affect only your PHP files, which would be the reason why other files are delivered with other headers.
However: Watch out when changing this. Maybe you would want this to be set for security reasons. Consider the problems with caching dynamic, authenticated content by proxies (link for detail)