Jump to content
xisto Community
Sign in to follow this  
spacewaste1405241471

406 Error I keep getting a 406 error...

Recommended Posts

Whenever I try to change my prefs for the e107 website hosted on Xisto i get a 406 error. I know its not a problem with the script, because I did a clean install of e107 to test it and it gave me the exact same error...I also got it when I tried updating my webblog for the site...But now the webblog works...But I still can't update my prefs...I'm pretty sure it is a server side problem...But could somebody please give me info on ways I could correct this. Thanks

Share this post


Link to post
Share on other sites

I found this link http://www.checkupdown.com/status/E406_de.html http://forums.xisto.com/no_longer_exists/ 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 '/'). 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

Share this post


Link to post
Share on other sites

YES!!!! MUSIC YOU ARE A GENUISE!...Fixed the problem temporarily... Now that I know what is going wrong...But how can I get it to allow the word system to be posted?Ok and yeah...Um did something change with the server to? Cuz I used to always be able to type system and have it work just fine....

Share this post


Link to post
Share on other sites

What mods have you installed? There could be an error in one of the or a bug in phpBB. try their website as well.If the problem continues, it may me server related and support will need to be contacted.Wish I could help more.

Share this post


Link to post
Share on other sites

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:)

Share this post


Link to post
Share on other sites

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.

Share this post


Link to post
Share on other sites

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

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
Sign in to follow this  

×
×
  • Create New...

Important Information

Terms of Use | Privacy Policy | Guidelines | We have placed cookies on your device to help make this website better. You can adjust your cookie settings, otherwise we'll assume you're okay to continue.