Modifiying 406 error messages triggered by Mod Security

[thobarn]

How can I modify the 406 returned by Mod Security triggers?

I am able to modify most other error documents on per domain basis by placing ErrorDocument directive to respective .htaccess files, and they work with the exception of 406 errors.

For example, in domain dummy.com docroot I have the following in .htaccess:
...
ErrorDocument 404 /[path_to_doc] (this works)
ErrorDocument 406 /[path_to_doc] (this does not)
...

When Mod Security triggers on dummy.com, a 406 is returned but it is not the customised 406 document given by ErrorDocument directive above


Thanks

[rhenderson]

Have you just tried 406.shtml in the root public_html? Just a thought.

[markhard]

well you don't want to copy the same file over and over again on all hosting account right?

[SuperBaby]

If it is for just one or two accounts, just edit look at the mod_security log which 406 page it is directing to. Then modify that page. This way, you do not need to edit your htaccess to include ErrorDocument 406 /[path_to_doc].

[rhenderson]

well you don't want to copy the same file over and over again on all hosting account right?

I appeared by the poster (since they were talking about an .htaccess file) this was for one account, but I could be wrong.

[thobarn]

Thanks for your replies. It turns out that it was the interaction with mod security. Any rule triggered in Phase 1 was causing the main server error documents to be served and not the ones defined in .httaccess in each virtual host ( because during P1 URL transformation is not yet performed by apache). Moving those rules to phase 2 resolved the issue. Thanks again.