Unrealistic but happy
- May 13, 2009
dfsfsfs"Oops! We ran into some problems."
I'm honestly getting beyond aggravated seeing this pop up all the time. I have to jump through hoops to put images in posts now, and even just changing the font size on two different lines can ruin a comment. What's going on with this?
Man, I had an issue with one of my posts too. I've had basically no problem editing most posts of mine. But for some reason, one of them REFUSES to edit, seemingly for no reason at all. No small text in there eitherA picture is worth a thousand complaints, so here's two:
As a test, PMs have now been enabled for Legacy and Escapist+ members. Please let me know if you run into any issues.Any news on the PM feature? We have digital keys sharing and we PM allows us to do so while avoiding Bots stealing them. Only other option is sort of doxing oneself.
Thanks for the detailed steps to reproduce this issue. I have verified the root cause. The posts with tons of markup trigger Cloudflare Web Application Firewall rules. When using that block of text above, the rule triggered is:I get the same error if I change the text color, font family, or font size, add a link, image, smiley or table, or change the font alignment. However, I can make it bold, italic, underline, or strike-through, add anything under the insert dropdown, or add a bullet list.
And here's the REALLY interesting part. With the first paragraph (starting with 'Uchikoshi') red, if I remove the parenthesis around (half) the error goes away, I can add (half) anywhere else in the post and it works, no other parentheses mess up the post anywhere. If I put one extra space before (half) it posts without error, but if I then write 'is (half)' anywhere else in the post it fails. But then if I delete most of the post I can post is (half) without error. This is crazy, I'm amazed I just happened to pick the exact perfect post for recreating an error like this on the first try at random. It's so specific, I can only imagine what kind of crazy stuff is going on behind the scenes to cause it.
Actually it seems like all that is required is: is (anything) to break it, doesn't have to be half but does need 'is' before parentheses... or 'in'... weirdly 'it' causes no error.
This seems to have worked! Thanks for the fix, and thanks to @Drathnoxis for that crazy thorough documentation!Thanks for the detailed steps to reproduce this issue. I have verified the root cause. The posts with tons of markup trigger Cloudflare Web Application Firewall rules. When using that block of text above, the rule triggered is:
This causes a 'challenge' CAPTCHA that causes the post submission to fail. I have made some adjustments that should fix this issue (or at least make it better).
- Inbound Anomaly Score Exceeded