Favicon 401 or 404 Error in Angular Single Page Applications (SPA)

This was an issue I recently encountered involving 401 & 404 HTTP errors generated for the Favicon.ico file in an Angular Single Page Application (SPA) that was built by a vendor that I’m servicing now for a customer.

Neither Chrome nor Microsoft Edge complained as much as Firefox did about the Favicon error. I can’t stand to see errors in applications so I had to find a way to solve this.

Luckily, after a bit of searching, I had found this discussion on StakeOverFlow about the Favicon throwing in error like this.

The Favicon Fix for Angular Apps

Use this “shortcut icon” tag instead of the favicon tag.

<link rel="shortcut icon" href="#">

This simple fix resolved my issue and I no longer see any 401 Unauthorized or 404 Not Found errors involving the favion.ico file in my Angular application.

As always, I hope this little snippet of knowledge helps someone. 😉

~Cyber Abyss

InfoSec Tip: What’s in those web server 404 NOT FOUND errors?

Catching Bad Guys using Web Server 404 Errors!

404 NOT FOUND pages in your web server logs are often the earliest sign of surveillance, foot printing or reconnaissance.

This probing event I caught was using the IP, bypassing DNS while probing for non-existent file called “/admin/config.php” all the way from Ramallah Palestine. #Infosec#OSINT#cybersecurity

Hope this helps someone!