Errors on posting/previewing

[SimonJM]

In SofaCitizen's Constructive Feedback/Request Thread I am getting server errors in replying or previewing:

"Internal Server Error
The server encountered an internal error or misconfiguration and was unable to complete your request.

Please contact the server administrator at webmaster@pfdlives.fantasiesrealm.com to inform them of the time this error occurred, and the actions you performed just before this error.

More information about this error may be available in the server error log.

Additionally, a 500 Internal Server Error error was encountered while trying to use an ErrorDocument to handle the request."

[SimonJM]

Problem circumvented - after a few tries of posting different things (mainly trying with and without the hyperlinks, etc.) I got it to work, but only by splitting the (not that long?) post into two and posting each half separately.

[SofaCitizen]

I had the same thing on this post: https://www.pfdlives.com/pfd/index.php?topic=8737.msg151372#msg151372

I never did figure out what was happening but there was something in that final paragraph that the code did not appreciate - but ONLY when combined with the earlier text. Posting it unedited by itself in a separate post was fine.

It would be very interesting to see what the logs have to say since I could not figure it out. My only current thoughts is it could be an over-eager ModSecurity config that is catching a certain combination of words/phrases within a POST request and thus blocking them. This would lead to a server error if not specifically checked for and handled I guess. However, in my (rather limited) experience the rules within a default config that most often produce false-positives where ones where certain SQL keywords were mentioned along with certain important punctuation. Neither of which I could see that I used in my post that failed.

[SimonJM]

I thought it could be something like that, too. But JUST by splitting the post into two (i.e., the exact same text, but in two separarte posts) alllows it to work. And that suggests a size issue over a content-based one. Well, to me, at least!