Create a gist now

Instantly share code, notes, and snippets.

How to short-circuit those annoying favicon requests in node.js
// early experiments with node had mysterious double requests
// turned out these were for the stoopid favicon
// here's how to short-circuit those requests
// and stop seeing 404 errors in your client console
var http = require('http');
http.createServer(function (q, r) {
// control for favicon
if (q.url === '/favicon.ico') {
r.writeHead(200, {'Content-Type': 'image/x-icon'} );
console.log('favicon requested');
// not the favicon? say hai
r.writeHead(200, {'Content-Type': 'text/plain'} );
r.write('Hello, world!');
console.log('Server running at');

Simple and sweet, thanks for sharing!


Glad it was useful!


In case someone stumbles upon this in the future.. If you are running nginx in front of node.js you can also block favicon requests by adding this line:

location = /favicon.ico { access_log off; log_not_found off; }

Wonderful, thanks.


This was very helpful. Thank you.




Thanks. This is exactly what I was looking for. Wish there were more useful, small code snippets like this around the Net.


Thanks so much! Exactly what I was looking for.




Great and simple! Thank you.


Thanks for this! Chrome causes this issue.


If you are using express you can do it like this

app.use(express.favicon(__dirname + '/public/favicon.ico'));

Great Solution without express! Thanks!


Thank you! Exactly what I was looking for. πŸ‘


Thanks... Once again.


Thanks that's what I was looking for πŸ‘




thanks for sharing πŸ‘


Great !!!!!


Nice one, thanks


God Bless you~


if you are interested I made and express middleware based on this gist; you can find it here:

// cc @kentbrew

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment