Javascript Disabled Detected

You currently have javascript disabled. Several functions may not work. Please re-enable javascript to access full functionality.


Welcome to AstaHost - Dear Guest , Please Register here to get Your own website. - Ask a Question / Express Opinion / Reply w/o Sign-Up!

Replying to 406 Error

Post Options

Enable emoticons?

Enter Your Name

Security Check *

[quote name="NilsC" post="20064" timestamp="1109603591"] I found this link [url="http://www.checkupdown.com/status/E406.html"]http://www.checkupdown.com/status/E406.html[/url] [url="http://tranchant.plus.com/notes/multiviews"]http://tranchant.plus.com/notes/multiviews[/url] 406 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle: * Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). * Open an IP socket connection to that IP address. * Write an HTTP data stream through that socket. * Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code that it recognises as '406'. Resolving 406 errors - general This error occurs very infrequently in Web browsers, because most browsers will accept any data returned from your Web server. If the client is not a Web browser, then anyone can only investigate the problem by looking at the Accept headers generated by the client system and the data stream returned by the Web server. If you do not have access to the source code for these systems, the only thing you can do is refer the problem to technical support people at the companies that developed the systems. Resolving 406 errors - CheckUpDown This error should simply never occur in your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages your site. We do not use accept headers at all, so there is no reason for your Web server to generate a 406 error. Please contact us (email preferred) whenever you encounter 406 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of your Web server software to agree the exact reason for the error. CheckUpDown logo We monitor your site for errors like 406. Please click any of the buttons below for more information. More about the service we provide Look at some examples of live accounts Try our service free for 90 days How much a LIVE account costs We respect your privacy More about our company and the Web sites we run[/quote] [quote name="NilsC" post="20064" timestamp="1109603591"] I found this link [url="http://www.checkupdown.com/status/E406.html"]http://www.checkupdown.com/status/E406.html[/url] [url="http://tranchant.plus.com/notes/multiviews"]http://tranchant.plus.com/notes/multiviews[/url] 406 errors in the HTTP cycle Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle: * Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs). * Open an IP socket connection to that IP address. * Write an HTTP data stream through that socket. * Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information. This error occurs in the final step above when the client receives an HTTP status code that it recognises as '406'. Resolving 406 errors - general This error occurs very infrequently in Web browsers, because most browsers will accept any data returned from your Web server. If the client is not a Web browser, then anyone can only investigate the problem by looking at the Accept headers generated by the client system and the data stream returned by the Web server. If you do not have access to the source code for these systems, the only thing you can do is refer the problem to technical support people at the companies that developed the systems. Resolving 406 errors - CheckUpDown This error should simply never occur in your CheckUpDown account. If it does, it typically indicates defective programming of our systems or of the Web server which manages your site. We do not use accept headers at all, so there is no reason for your Web server to generate a 406 error. Please contact us (email preferred) whenever you encounter 406 errors - there is nothing you can do to sort them out. We then have to liaise with your ISP and the vendor of your Web server software to agree the exact reason for the error. CheckUpDown logo We monitor your site for errors like 406. Please click any of the buttons below for more information. More about the service we provide Look at some examples of live accounts Try our service free for 90 days How much a LIVE account costs We respect your privacy More about our company and the Web sites we run[/quote]

or Cancel

Topic Summary

FirefoxRocks

Posted 17 September 2007 - 03:45 AM

So a 406 Error is:

The server can only generate a response that is not accepted by the client

What kind of response/data would that be anyways?

hihihihi88

Posted 02 March 2005 - 12:11 PM

I must thank to vujsa coz u find the problem and send the PM .

vujsa

Posted 02 March 2005 - 03:43 AM

If I'm not wrong... Someone has already posted how to do the convertion in one of the tutorails... It is quite recent too!
<{POST_SNAPBACK}>

Actually, I think that that may have been me but that wasn't the solution.

It appears that the error has been corrected.

Many thanks to OpaQue.

Happy coding,

vujsa

Xevian

Posted 01 March 2005 - 01:00 PM

If I'm not wrong... Someone has already posted how to do the convertion in one of the tutorails... It is quite recent too!

I'm sorry, I didn't know what e107 was.

I had phpBB installed on my home test platform with out problem. Now that My site is running I have SMF running on it and as you allready know, it will not process the word "system".

The only explaination for this is that Apache has be intentionally configured to dissallow the word system. Probably to prevent hackers from accessing root:system:etc ...

Sample from my Apache access log file:

/scripts/..%255c%255c../winnt/system32/cmd.exe?/c+dir

Hacking attempt!

The only solution is for OpaQue to modify the httpd.conf to allow the word "system" but maintain security.

I'll PM him and make the suggestion.

vujsa

[Edit]

Sent a PM to OpaQue to have him look into the problem.

hihihihi88

Posted 01 March 2005 - 05:02 AM

I am sure that not the problme on phpBB or e107, coz i install a BBS written in CGI . It also can't post contant "system" .

spacewaste

Posted 01 March 2005 - 04:21 AM

I'm using e107 not phpbb...And the problem recently started happening... So I am just assuming something with the server changed

Oh welll...I'm looking around for a script to work with my portal that would convert system to sys_tem and then back to system

I am now know what problem happenning...
not the phpBB script
it is the server something changing
<{POST_SNAPBACK}>

hihihihi88 had the same problem but must have found a solution. He didn't specify what.

vujsa

Review the complete topic (launches new window)