1

UPDATE

learning that application/javascript has been deprecated, this has now been updated to read: text/javascript. Issue persists.

I have verified that this is not an actual 404. a file of that name exists at that path, with ownership and permissions which should make it accessible to the webserver user.

Following Marcus Müller's suggestion below, that the AddType directives I added years ago to an apache2 virtual host template are now redundant, I commented those out, and ran a stop / start on apache and the php-fpm. I'm still seeing the same results in the network tab.

enter image description here

for a couple of years now, my apache2 virtual host containers include, in the top scope, unaffected by conditionals, these two lines:

AddType text/css .css
AddType application/javascript .js

and there is this:

$ apache2ctl -M | grep mime
 mime_module (shared)

still the firefox network tab reports that multiple files are giving me 404s, and errors reading: NS_ERROR_CORRUPTED_CONTENT.

Each is clearly identified with their .css or .js extensions and are all being seen in the browser as malformed html code.

Any thoughts on how to further diagnose or resolve this issue would be greatly appreciated.

-- Hugh Esco

Improve this question

1 Answer 1

Reset to default
1

HTTP 404 is pretty unambigous: the requested resource cannot be found. For errors like "the browser said it'd accept CSS only, but what it requested is a PNG", there's other error codes.

So, the direction in which you need to dig is why the URLs your browser is requesting can't be found on your server. This is likely unrelated to your mime_module or the AddType directives. (Also, your AddType directives seem redundant: these are default settings on any default mime.types config on any machine I've worked with in the last ~ 20 years!)

Improve this answer
2
  • Except that I have confirmed at the cli, that files with these names exist at this path and have ownership and perms making it accessible to the www-data user. Commented May 28 at 21:31
  • well, the server is clear about "not found"; so you must have looked in a different location than the server does. I'd recommend checking the access or error logs of your server – these 404'ed requests should show up in there. Commented May 29 at 8:44

You must log in to answer this question.

Start asking to get answers

Find the answer to your question by asking.

Ask question

Explore related questions

See similar questions with these tags.