Skip to content

Comment on How A Missing Favicon Broke My App for Chrome Usersparent

Comments

Not a dangerous setup as much as a misconfigured one with dangerous side effects.

The problem is easily resolved by having Apache respond with a 404 to any requests for non-existant static resources. Which is of course what it should be doing in the first place.

If you have bad links, and this PHP scheme, then Google will probably flag you for duplicate content issues too.

AboutSource Built by g1lg1l

Hackerly is an independent reader for Hacker News, built on the public HN API. Not affiliated with Y Combinator.