This is a ModSecurity test post.

I want to confirm that ordinary user-submitted text is no longer being inspected by the OWASP CRS argument rules.

Some harmless phrases for testing:

select from the menu union meeting tonight drop the package at the front desk insert the key into the lock update the document tomorrow delete the old draft sleep for eight hours system administrator command line execute the plan whoami is a funny username curling is a winter sport wget sounds like a typo script writing shell game base64 encoding eval is short for evaluation

Here are some punctuation-heavy examples:

can't won't shouldn't haven't "quoted text" 'more quoted text' (parentheses) [brackets] {braces} one; two; three one && two one || two $HOME /path/to/something ../example/path

Some URL-like text:

https://example.com/test example.com/path?q=hello&value=world /forums/test.php?id=123&sort=new

Some technical-looking but harmless prose:

The user said "select the first option from the list." The administrator told me to update the system after lunch. I need to delete the old file and insert the new information. The word command appears several times in this paragraph. The word shell also appears here. The phrase execute the plan is normal English.

And some longer natural language:

If a user writes a long post about programming, Linux, databases, web development, or server administration, they may naturally use words such as command, shell, select, union, insert, update, delete, script, system, process, execute, curl, or wget. A discussion forum should not reject a legitimate post merely because those words happen to resemble tokens used in security attacks.

This message contains intentionally awkward combinations of technical words, punctuation, paths, URLs, symbols, contractions, and ordinary English. If the forum accepts this message normally, that is a good indication that ModSecurity is no longer inspecting the contents of GET and POST arguments with the OWASP CRS rules.

End of test.