Keep being sent home.

[NickJ]

The mod_security is a web application intrusion detection and prevention engine. It operates by 'hook'ing itself into apache and inspecting all requests for your specific ruleset. It can be used to monitor your server with logging or even protect it by denying attacks.

The mod_security module gives Apache Web server increased ability to inspect and process input from Web clients before it's acted on by the scripts or processes waiting for the input.

We understand that these changes will certainly affect your website hosting administration in one way or another. However, our top priority here is to protect our servers and data.

Commenting out a line in a mod_security configuration or exclude affected domain from mod_security restriction is a workaround, but it would be potential increase in site-wide risk for vulnerability to cross-site scripting attack.
A better workaround, does not blindly remove the filter for all applications.

[DPS Computing]

Thanks for posting on here Nick - I understand that you are probably a very busy person but am pleased that you have taken the time to become a member and hopefully we will see more posts from you in the future.

What is the "better workaround" that you mentioned then - or is this specifically done on a case by case basis?

[NickJ]

Thank you, David.

Its depend upon the rules affecting the application and the absolute path for the directory under which the application is installed. As I mentioned in my previous post there is no direct workaround for it other than commenting out the rules or excluding domain from the restriction.
Still I am working on customizing the rule set, so that it wont block legitimate application but it would take time. I don't have exact ETA on it but will try to implement it asap.

[DPS Computing]

Originally Posted by NickJ

Thank you, David.

Its depend upon the rules affecting the application and the absolute path for the directory under which the application is installed. As I mentioned in my previous post there is no direct workaround for it other than commenting out the rules or excluding domain from the restriction.
Still I am working on customizing the rule set, so that it wont block legitimate application but it would take time. I don't have exact ETA on it but will try to implement it asap.

Well good luck with modifying the rules - I am sure you will do the best you can for us!!