Comments on: Is your browser requesting a page twice?

By: Acevado

Acevado — Fri, 12 Mar 2010 04:21:31 +0000

Thanks for these hints!

I had neither missing or wrong charset meta definition nor the wrong charset for my content, but the problem was reoated to international characters (german umlauts in my case).

*After disabling the Firefox charset encoding auto detection the problem disappeared.*

Don’t know though why FF should even try to autodetect if there’s a charset meta header available…;

By: michael

michael — Sun, 07 Feb 2010 11:37:45 +0000

Thanks for these hints!

I had neither missing or wrong charset meta definition nor the wrong charset for my content, but the problem was related to international characters (german umlauts in my case).

*After disabling the Firefox charset encoding auto detection the problem disappeared.*

Don’t know though why FF should even try to autodetect if there’s a charset meta header available…

By: split

split — Thu, 10 Dec 2009 21:45:55 +0000

Hey. In my case firebug caused the second request.

By: tmi

tmi — Tue, 08 Sep 2009 09:11:20 +0000

In my case it was the combination of

Firefox 3 and

that caused the requests to be executed twice.

After changing the charset from iso-8859-15 to iso-8859-1 my application worked fine.

By: hi

hi — Sun, 05 Apr 2009 02:59:43 +0000

This happens also with null objects / flash applets too. Make sure all your src’s aren’t null.

Was driving me nuts until i found this little bugger….

By: ffx

ffx — Thu, 12 Feb 2009 15:17:25 +0000

Here is another example:

In this case, if styleSheetName is an empty string, the page will also be requested twice.

By: sick pig

sick pig — Fri, 14 Nov 2008 03:28:25 +0000

Try again.

So the solution was

instead of

By: sick pig

sick pig — Fri, 14 Nov 2008 03:26:49 +0000

Same deal in a page where the src is set by js in response to the user making a choice in a drop-down. So the solution was

instead of

By: Yermo

Yermo — Wed, 15 Oct 2008 21:49:34 +0000

Just ran into this problem in FF 3.

To avoid this problem how can you, on the server, recognize whether or not a given request is coming from an empty img src=”"? MSIE seems to set the HTTP_ACCEPT header to */* on reload and doesn’t distringuish between img and page requests.

By: Ian

Ian — Wed, 01 Oct 2008 13:58:14 +0000

Thanks for posting this. Saved me losing all my hair.
For me it turned out to be some nifty java script I had inherited pre-processing pages (and img tags).

Thanks again.