17452 Posts in 4473 Topics by 1971 members
|Go to End|
3 July 2008 at 2:58pm Last edited: 3 July 2008 2:59pm
I just set up Silverstripe on a web server. Everything went well and there were no error messages during the installation process. However, when I am in the CMS (backend) and I click on any link in the left hand menu (site tree or assets folders, etc) I get the following error message:
"501 Not Implemented
The page you are looking for cannot be displayed because a header value in the request does not match certain configuration settings on the Web server."
Does anyone what that message means or what could be the problem or configuration setting the error message mentions? The web server software is Apache (BSD). Thank you!
7 July 2008 at 1:16pm
SilverStripe doesn't generate any 501 errors, so this is most likely to do with your webserver configuration. I suggest you talk to the sysadmins.
It might have something to do with the browser you're using too.
8 July 2008 at 9:41am Last edited: 8 July 2008 9:42am
thank you for your reply. The error message is probably generated by the web server. I also checked the error log and it comes up with this message:
[Tue Jul 08 09:17:54 2008] [error] [client xxx.xxx.xxx.xxx] ModSecurity: Access denied with code 501 (phase 1). Match of "rx (?:^(?:application/x-www-form-urlencoded$|multipart/form-data;)|text/xml)" against "REQUEST_HEADERS:Content-Type" required. [id "960010"] [msg "Request content encoding is not allowed by policy"] [severity "WARNING"] [hostname "domain.name.co.nz"] [uri "/new/admin/getitem?ID=1&ajax=1"] [unique_id "m9hWIdIFMgMAAHemQAUAAAAI"]
I am using Firefox 3 and IE 7 (Windows). I can use other Silverstripe installations on different servers without any problem.
If anyone had a similar problem or can point me to the right direction I would be very grateful. ModSecurity seems to cause the problem but I don't know what setting would need to be changed.
8 July 2008 at 11:09am
the problem is solved. Unfortunately I don't know about the details but it all has to do with an implemented "ModSecurity thing". The hosting company changed a setting and now the Silverstripe CMS works as expected.
|Go to Top|