But it was instantly 'Forbidden'. There's no way you had time to check it. You have a bug on the site.
Also, it's not very objective to have 'reviews' that are checked by the owner before being posted. What's to stop you cherry picking only the good ones?
Anonymous A (OP) replied with this 6 years ago, 35 seconds later, 3 hours after the original post[^][v]#1,057,386
@previous (E)
If I disapprove a review once, that reviewer is banned from reviewing again. It prevents trolls.
Anonymous F replied with this 6 years ago, 3 minutes later, 3 hours after the original post[^][v]#1,057,387
@previous (A) > If I disapprove a review once, that reviewer is banned from reviewing again. It prevents trolls.
Will you allow me to make a review containing the words "girlturd" and "pronounced as one word"?
Anonymous E replied with this 6 years ago, 3 minutes later, 3 hours after the original post[^][v]#1,057,390
> If I disapprove a review once, that reviewer is banned from reviewing again. It prevents trolls.
I tried to submit once only and it was automatically rejected. You didn't review it. You have a bug dude.
Anonymous F replied with this 6 years ago, 2 minutes later, 3 hours after the original post[^][v]#1,057,391
@previous (E) > I tried to submit once only and it was automatically rejected. You didn't review it. You have a bug dude.
If it was a bug it would throw a 500, not a 403. Seems legit if you're trying to write a spam/troll review.
Anonymous A (OP) replied with this 6 years ago, 1 minute later, 3 hours after the original post[^][v]#1,057,392
Anonymous G joined in and replied with this 6 years ago, 2 hours later, 5 hours after the original post[^][v]#1,057,467
@1,057,391 (F)
I mean, no, not necessarily. A bug could cause any status code to be returned.
Anonymous C replied with this 6 years ago, 1 hour later, 6 hours after the original post[^][v]#1,057,489
Syntax is finished here!
Anonymous F replied with this 6 years ago, 21 minutes later, 7 hours after the original post[^][v]#1,057,497
@1,057,467 (G) > I mean, no, not necessarily. A bug could cause any status code to be returned.
My point is it's not a generic bug (like a null pointer exception or something) which would result in a 500, but specifically 403 / Forbidden. 403 usually implies that read/write permissions to some resource or other on the server are not set correctly. It's probably the write permissions on the DB. Bug == programming fuckup -> 500. Permissions -> 403.
Anonymous H joined in and replied with this 6 years ago, 3 hours later, 10 hours after the original post[^][v]#1,057,583
Anonymous G replied with this 6 years ago, 5 hours later, 16 hours after the original post[^][v]#1,057,678
@1,057,497 (F)
That likely is the case, but it doesn't necessarily have to be. Plenty of bugs can mean 4xx errors are thrown, especially if you're doing any status code handling directly. You're probably right in this situation, but "If it was a bug it would throw a 500, not a 403" just isn't true. I've written plenty of code that ends up with 403/404/418. ?