Welcome to WebmasterWorld Guest from 54.226.183.49

Forum Moderators: incrediBILL

Message Too Old, No Replies

HTTP 406 Error on Vista with IE 7

     

penstaar

6:41 pm on Sep 18, 2008 (gmt 0)

5+ Year Member



Hi there,

My friend's site has a signup page for a newsletter. When people on Vista with IE7 try to sign up they receive the error message below. Users on XP with IE7 are fine.

I don't think I can post the link here, but has anyone else encountered this?

I can PM you the link you think you can help.

Thanks!

----

Internet Explorer cannot read this webpage format

HTTP 406

What you can try:

Go back to the previous page.

More information
This error (HTTP 406 Not Acceptable) means that Internet Explorer was able to receive information from the website you visited, but the information was not in a format that Internet Explorer can display.

For more information about HTTP errors, see Help.

jdMorgan

7:08 pm on Sep 18, 2008 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member



Check the server headers and see what Content-Type (MIME-type) header is returned using Firefox and the Live HTTP Headers add-on. Compare this Content-Type to the Accept header in the browser request.

There are three most-likely possibilities: First, perhaps the server has not been configured to return the correct Content-Type along with the page. For example, the page is application/xhtml+xml but the content-type says it's text/html.

Second, maybe the page itself is encoded improperly -- possibly because it was written with a word processor (e.g. MS Word) instead of an HTML or text editor or a WYSIWYG Webpage editor, or because it was exported from one of these tools in the wrong format (something other than plain text using ISO-8859-1, UTF-8, or a similar standard character-set).

Third, it's possible the page got corrupted because it was uploaded using incorrect format settings in FTP or whatever program was used to put it on the server.

There are other possibilities. These are just the first that come to mind.

Jim

penstaar

7:58 pm on Sep 18, 2008 (gmt 0)

5+ Year Member



Hi jd,

I'm not sure what you mean by "Accept header in the browser request" but I can tell you that the thank you page is .asp and the Content-type returned was text/html.

So you are suggesting that could be the problem?

Here is the source:

<HTML>
<HEAD>
<META NAME="GENERATOR" Content="Microsoft Visual InterDev 1.0">
<META HTTP-EQUIV="Content-Type"
content="text/html;charset=iso-8859-1">
<TITLE>CDONTSMail</TITLE>


</HEAD>
<BODY>

Welcome! Thank you for subscribing to our weekly software tips.<br>You'll soon receive an e-mail confirming your subscription.<br><br><a href='http://www.mysite.com/'>Done</a><br>
</BODY>
</HTML>

g1smd

8:13 pm on Sep 18, 2008 (gmt 0)

WebmasterWorld Senior Member g1smd is a WebmasterWorld Top Contributor of All Time 10+ Year Member Top Contributors Of The Month



You need to be looking at the HTTP headers, and not the <head> section of the HTML page.

You will need the Live HTTP Headers extension for Mozilla Firefox in order to see that data.

It will show you exactly what your browser requests of the website, and the HTTP preamble that is returned by the server before the HTML page is sent.

penstaar

9:19 pm on Sep 18, 2008 (gmt 0)

5+ Year Member



Jim,

The Accept header shows:
Accept: text/html,application/xhtml+xml,application/xml;q=0.9,*/*;q=0.8

The Content-type header shows:
Content-Type: text/html

So does this mean that the problem was your first suggestion that the server has not been configured to return the correct Content-Type along with the page?

Thanks

jdMorgan

10:26 pm on Sep 18, 2008 (gmt 0)

WebmasterWorld Senior Member jdmorgan is a WebmasterWorld Top Contributor of All Time 10+ Year Member



No, your own page declares itself as text/html, so the server headers are in agreement with that. The fact that it's generated by .asp matters not a bit.

Do be sure you are looking at the page that generates the 406 error when viewed with IE7. Also check all of the included images, scripts, css files, etc. -- You will see all of these in the Live HTTP Headers dump.

It's kind of a problem debugging with Firefox/Live Headers, because you can't see what happens with IE. Unfortunately there is no comparable headers tool for IE, and the on-line headers checkers are notorious for omitting not only some of the headers, but even some of the transactions (like redirects).

Anyway, check all the included objects on the page that errors out, and make sure their content-types make sense... text/css, image/gif, image/x-icon, image/jpeg, etc.

Jim

 

Featured Threads

Hot Threads This Week

Hot Threads This Month