CMS v2.65 This Site says... There was an error sending the request! (403 Forbidden)

Okay just discover I had run the phpinfo in the wrong location.  Had run it in the root directory.  I have now run it in the public_html directory and cgi.force_redirect shows value of 1 for local value and 1 for Master value. 

Hi John, 

 cgi.force_redirect shows value of 1 for local value and 1 for Master value. 

Are you attempting to change the cgi.force_redirect  setting because of  this post:

http://www.interactivetools.com/forum/forum-posts.php?postNum=2237567#post2237567

I think in this case the issue might be because of mod-security, you can find more details on this here:

http://www.interactivetools.com/forum/forum-posts.php?postNum=2236533#post2236533

Please could you check with your host if mod security is enabled, and if it is, ask them to disable it? 

If that doesn't work you can fill out a second level support request here:

https://www.interactivetools.com/support/email_support_form.php

and we can take a closer look at the issue. 

Cheers!

Greg

Thank you for all the help.  Greatly appreciated.  My host was able to resolve the issue for me after a second try.

Greatly appreciative

John

Hi John,

Any idea what steps your host took to resolve this issue?

Cheers,

Jayme

Hi Jayme

The only information they gave me is that they disabled a couple of "mod_security rules" that were blocking the pages

Sorry I don't have more info.

John

This is useful. Thanks John.

I'm starting to see this error more and more these days - and on a wider range of our sites.

It normally appears when trying to modify an existing editor field with Advanced settings on a production server. So if you're saving the extra field settings in a lightbox, that's when the error usually appears. "Top Level" changes to the editor, don't seem to trigger this error. I'm guessing it has something to do with the file being loaded into the lightbox for editing.

We've found two work-around so far:

1. Change the editor on another server and FTP the schema over.
2. Manully edit the schema on the production serve and then revisit the Section Editors after doing so.

QUESTION:

Is there a clear directive we can ask our hosts for that would solve this issue? It's affecting a larger number of our sites these days and I don't want to have issue a trouble ticket for each domain if I can help it.

Many thanks,

Jayme

Thanks Greg. This seems to be more of an issue on one host even though both appear to have mod_security active.

Just for discussion, I would think that we'd rather have mod_security running than not though. Although you pros at Interactive Tools probably validate and clean your code, other functions on sites might not have received the same care. This library provides some blanket protections again DDOS and malicious form injections which I'd rather have on if possible. Any thoughts?

Jayme