Still no luck... I logged into my server's WHM and checked its Mod Security application. Here's another tidbit of info pertaining to the errors that might help you determine the root of this problem:
Access denied with code 403 (phase 2). Pattern match "\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})" at ARGS:wysiwyg_content. [file "/usr/local/apache/conf/modsec2.user.conf"] [line "20"] [id "950107"] [msg "URL Encoding Abuse Attack Attempt"] [severity "WARNING"]
I could edit the Mod Security config file which might help allow this problem pass through, but I'm wondering if it may create a security hole in the server. This is the line it's referring to in the modsec2... configuration file:
# Check decodings
SecRule REQUEST_FILENAME|ARGS|ARGS_NAMES|REQUEST_HEADERS|!REQUEST_HEADERS:Referer "@validateUrlEncoding" \
"chain, deny,log,auditlog,msg:'URL Encoding Abuse Attack Attempt',id:'950107',severity:'4'"
SecRule REQUEST_FILENAME|ARGS|ARGS_NAMES|REQUEST_HEADERS|!REQUEST_HEADERS:Referer "\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})"
Suggestions?
Access denied with code 403 (phase 2). Pattern match "\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})" at ARGS:wysiwyg_content. [file "/usr/local/apache/conf/modsec2.user.conf"] [line "20"] [id "950107"] [msg "URL Encoding Abuse Attack Attempt"] [severity "WARNING"]
I could edit the Mod Security config file which might help allow this problem pass through, but I'm wondering if it may create a security hole in the server. This is the line it's referring to in the modsec2... configuration file:
# Check decodings
SecRule REQUEST_FILENAME|ARGS|ARGS_NAMES|REQUEST_HEADERS|!REQUEST_HEADERS:Referer "@validateUrlEncoding" \
"chain, deny,log,auditlog,msg:'URL Encoding Abuse Attack Attempt',id:'950107',severity:'4'"
SecRule REQUEST_FILENAME|ARGS|ARGS_NAMES|REQUEST_HEADERS|!REQUEST_HEADERS:Referer "\%(?![0-9a-fA-F]{2}|u[0-9a-fA-F]{4})"
Suggestions?