403 Forbidden

My 403 Forbidden post was on the Military Aircraft board.  Yet I am able to post on this board just fine.

Aggieman

I know what this means as a software engineer, but damn if this is not irritating given that I just wrote up a long post on my latest builds.

Any idea on work-arounds or how long this will be happening? 

This is a recurring bug; the most recent report of it before your post is this one:

https://cs.finescale.com/fsm/feedback_help_and_testing/f/39/t/190413.aspx

No word about when it might be resolved.

A workaround is to clear your browser cache and then access the forum in a new session.  That seems to work for most of the people who have reported it.

Aggieman

I know what this means as a software engineer, but damn if this is not irritating given that I just wrote up a long post on my latest builds.

Any idea on work-arounds or how long this will be happening?

I have learned by experience that if i spend a long time writing a post on this forum, to copy the entire text with my cursor.

Too many times I've clicked "submit your reply" and gotten an error. Then when I go back, the entire text of my lenghty post is gone.

Now, I click reply again and paste the text into the new window.

In fact, Rob taught me to write a long post in word and then cut/ paste into a new post. Can't do that on my phone, but I don't post much from it except short comments.

Bill

Not sure if it's related- might be for a 403 but if I change networks I have to re-authenticate.  I've experiened this on my mobile phone.

GMorrison

In fact, Rob taught me to write a long post in word and then cut/ paste into a new post. Can't do that on my phone, but I don't post much from it except short comments.

 

Bill

If I use my phone, I type the draft into an email.

Aggieman

I know what this means as a software engineer, but damn if this is not irritating given that I just wrote up a long post on my latest builds.

Any idea on work-arounds or how long this will be happening?

 

Hi Aggieman,

Sorry for coming to the thread late. Needless to say, I'm unhappy to see this error popping up again. Baron and others have given you pointers for circumventing it, and I'll pop it back on the list of things we need to revisit.

Here's another case in which we could use a Like button