Guestbook/Comments not posting?

Permalink
I have installed concrete 5.4.2.2 for two different clients and have noticed that the comments won't work?

If you have a look at:http://info.kjgraphics.co.uk/index.php/about/guest-book/...

and try and add a comment (this is still just the standard sample content site with no modifications) you get this error:

Not Acceptable

An appropriate representation of the requested resource /index.php could not be found on this server.
Additionally, a 404 Not Found error was encountered while trying to use an ErrorDocument to handle the request.

with this written as the url: http://info.kjgraphics.co.uk/index.php?cID=70&bID=27&arHand...

I have this error on both installs. I also have two other install's working with the same provider? Has anyone got any ideas what may be causing this issue?

Any help would be really appreciated 'cause I have no idea where to look?


PS: if you have "pretty UR:'s" it goes to the standard page not found but still has the 'ugly' URL.

 
jjcdesign replied on at Permalink Best Answer Reply
Incase anyone else gets this problem, my solution was....

Contact your host and check the server settings because this was to do with the passthru function being mentioned in the URL. Their servers do not allow the passthru function, so it was recognising this and stopping it from working (although on a newer server it worked). Their mod_security has now been changed to allow the passthru in the URL whilst still not allowing the actual php function. (this all goes over my head but hey, it now works!). They said:

"The passthru function is disallowed on all of our servers, however in the case of concrete5, it's the parameters in the URL that are being scanned by a security layer called mod_security. Concrete5 will not actually be using the php passthru function, it's just that the parameter in the URL is being disallowed.

I have therefore removed the 'passthru' string from the URL checking in mod_security on the server so that your concrete5 will run. This does not actually reduce security since, as I say, the actual php function itself is disabled."

Hopefully this may help anyone who gets a similar problem.