Just got it again. Wish it was at least consistent, I can plan around a consistent issue. It randomly deciding that it has been too lenient on how long it gives me and halving that time? That I can not plan around.
The issue is becoming really annoying... now i am not able to post a new thread (the entry thread for the new painting comp.) Update: i'm trying to circumvent the issue, but it's really hard, and i'm obtaining only marginal successes. It's frustrating
...and once it gives you the error on a post... bam, it's deader than dead, you are no more able to edit it. I need to try the "delete" option
The issue really doesn't want me to post on the GW news thread - by the looks of it, it's happening for me when I copy-paste some text from elsewhere as the basis for my post. Though, of course, that's probably not what's causing it to occur for other people's posts...
the problem is... sometimes copy-paste triggers it, sometime don't. Sometime it happens without copy-paste... and so on
Thanks for the feedback, I'll start digging into this today, but it might take a few days to get it sorted. A quick follow-up question: After the 403 error happens, are you able to browse the website normally, just not reply/post to that thread?
Can browse normally and even reply/post on other threads, it just locks me out of replying to the thread where I got the error for however long.
I have managed to locate a log entry on the webserver from today from a 403, but it unfortunately does not explain what is happening, as it just tells it terminated the request. The question is what part of the server system that "decided" to terminate the request. I have tried having an edit open to trigger it on my side, but have so far not been able to duplicate the problem.
After maybe 5 or so attempts to post something in short succession the site can become completely unresponsive, as in, I'll get an error response instead of the site for an hour or so. Not sure if this is just an anti-spam response though. I might be able to reliably reproduce the error, but it might be user-specific. Let me have a go and see what happens...