It happens again, this time the post is short, I think there is banned words that prevents posting and returning 403 but I can't figure it out.

whole content that I wanted to post is available here: http://rtfreesoft.blogspot.com/2018/07/new-build-of-browsers-for-win2000.html

31 minutes ago, roytam1 said:

I think there is banned words that prevents posting and returning 403 but I can't figure it out.

It's just the current buggy IP.B!
There's nothing in particular causing it, it seems to be fully random, in fact.

Bad word filter is working properly. This new version is even "smart" enough to no longer censor Fukushima!

redacted

 

^ when these two lines join together, 403 is issued.

Edited July 20, 20188 yr by Tripredacus

^ Confirmed!

Doesn't seem to have anything to do with the words. Changing them still has the error, but something like 1::2 doesn't cause a problem.

The error-causing string which roytam1 couldn't post here:
https://msfn.org/board/topic/133014-last-versions-of-software-for-windows-2000/?page=11
...is the ultrashort changelog as in his blog, just 2-lines:
http://rtfreesoft.blogspot.com/2018/07/new-build-of-browsers-for-win2000.html

Strange that here in his reporting post the reported string is now deleted as "redacted", removing all hints about possible reasons, and my test post containing a modified changelog was just deleted completely: https://msfn.org/board/topic/133014-last-versions-of-software-for-windows-2000/?page=11

At first had suspected the duplicate double-dots (colons) and tried variations of those, because the MSFN software had some bad bug with double-minusses before the last update.
But perhaps it's rather the combination of "data" followed by a colon? Could be abused for data-URIs, like base64 images or split-screen URLs.
At least in this case. Not likely that all the other bug-posters used "data" too.

Regarding the post length limit, I don't think the last lengthier post I tried to write on this forum was the longest I wrote here. But even if it was too long, the error message should be descriptive.

Today I got 403 error again. The reason was embedding link to another post on the forum. When I changed it to plain text hyperlink, the post was accepted. You can also try previewing your post with a link embedded like that; the preview will be empty.

Wasn't it also possible to embed links to albums on imgur like that?

On 7/20/2018 at 3:20 PM, siria said:

Strange that here in his reporting post the reported string is now deleted as "redacted", removing all hints about possible reasons

It is due to the nature of the data, which was not alluded to here. The string has been posted in the private section of the forum. It is a best practice to not leave bugged code in public view once it has been identified. That was the reason it was removed.

Text from @roytam1 posts causing an error seems to be fixed. Please let us know if  we have any more of these 403 errors starting from now.

{nsUXThemeData::drawThemeEdge}