double requests from Chrome

[Mark Volkmann]

Here's a very simple HTTP server:

var http = require('http');

http.createServer(function (req, res) {

  console.log('got a request');

  res.writeHead(200);

  res.end('Hello, World!');

}).listen(3002);

When I hit this from Chrome, "got a request" is output twice and two more times every time I refresh the page in the browser.

However, when I do this from Firefox I only see "got a request" once for each refresh.

Does anyone know why Chrome is sending duplicate requests and what I can do to avoid this?

--
R. Mark Volkmann
Object Computing, Inc.

[Chris Rhoden]

It is attempting to download favicon.ico

chrisrhoden, from my telephone.

--
Job Board: http://jobs.nodejs.org/
Posting guidelines: https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
You received this message because you are subscribed to the Google
Groups "nodejs" group.
To post to this group, send email to nod...@googlegroups.com
To unsubscribe from this group, send email to
nodejs+un...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/nodejs?hl=en?hl=en

[Ben Noordhuis]

It's a bug in Chrome where it keeps trying to download /favicon.ico

http://code.google.com/p/chromium/issues/detail?id=39402

[Ryan Doenges]

yep, it's GETting /favicon.ico.

this has gotten me before, it is really irritating.

> --
> Job Board: http://jobs.nodejs.org/
> Posting guidelines:
> https://github.com/joyent/node/wiki/Mailing-List-Posting-Guidelines
> You received this message because you are subscribed to the Google
> Groups "nodejs" group.
> To post to this group, send email to nod...@googlegroups.com
> To unsubscribe from this group, send email to
> nodejs+un...@googlegroups.com
> For more options, visit this group at
> http://groups.google.com/group/nodejs?hl=en?hl=en
>

--
Ryan Doenges

[Matt]

Another thing chrome does - if you have an iframe with src="#" (rather than src="") which you're going to display/hide later, Chrome will request the page twice.

[Isaac Schlueter]

I personally think this behavior is fine. Just serve a /favicon.ico
or a fast 404 when requested. HEAD should always be safe and
idempotent.

[Christopher Jeffrey]

> Another thing chrome does...

This isn't just chrome. Every browser since the 90s automatically
requests /favicon.ico.

[Will Wen Gunn]

Every Browser will automatically requests /favicon.ico file.

2012/2/6 Christopher Jeffrey <chjje...@gmail.com>

> Another thing chrome does...

This isn't just chrome. Every browser since the 90s automatically
requests /favicon.ico.

[Isaac Schlueter]

The thing that chrome does differently is request *again* if the
server responds with a non-favicon or non-200 response.

[Christopher Jeffrey]

Will Wen Gunn wrote:
> Every Browser will automatically requests /favicon.ico file.

I agree. Did I say something different?

Isaac Schlueter wrote:
> The thing that chrome does differently is request *again* if the
server responds with a non-favicon or non-200 response.

Ah, I see now.