We have noticed through our web server access logs and monitoring tool (Dynatrace) that Chrome ignores the <html> tag for the location of the *.ico file. This is very minor, but CPU cycles are being wasted looking for this resource. Chrome doesn’t cache it either. The issue has to do with SSO and alternative sign on pages, but the easily reproduced step is to go to http://<tririga.server.com>/favicon.ico and it will show a 404 error.
There was no mapping to the favicon.ico directly in the web.xml. Moving forward, when the browser requests the default favicon.ico, the favicon configured in the /userfiles/icons is now sent to the browser, instead of getting a “404 Not Found”.