First and foremost, thanks for recognizing me 
Anyways, I keep getting the following error too often; at least once every other forum visit. It is worth noting that the time in which I have been directed to this error white page, for that's what it is a 1998 error page, has been during the submission of 2 paragraphs worth of text.
------
Request Entity Too Large
The requested resource
/t5/forums/replypage.editorform.form.form.form
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
------
I've come to notice the WYSIWYG text editor sometimes inject redundant code inserts extra HTML tags and/or fails to properly delete associated HTML markup when one deletes the text on the WYSIWYG interface. Perhaps this excess of code could be the problem.
Moreover, why is the error even telling me "does not allow request data with POST requests" I'm not requesting data [GET] from the servers; I'm posting [POST] a message to the server. The editor needs fixing.
I know your question was probably to the OP, but I received the error message pasted below at least 2/3 times, I use Chrome running on a MacBook.
Request Entity Too Large
The requested resource
/t5/forums/replypage.editorform.form.form.form
does not allow request data with POST requests, or the amount of data provided in the request exceeds the capacity limit.
PSX_Cheatster wrote:What do you mean by "inject redundant code"? What browser/OS are you using, if you don't mind me asking?
Hello there PSX_Cheatster. SevenFactors here 
"inject redundant code" was a very poor use of word by me. It's not that I found a vulnerability that could be exploited nor anything like it.
My recent post-history is formed by a combination of bullet list, bold test, italics and few colored text. I also copy/paste, as fit, content from Knowledge Center/Support pages.
I looks like sometimes between the text formatting/editing and/or copy & pasting, the text editor adds extra HTML tags and/or when deleting text from the WYSIWYG editor the associated HTML tags don't get removed from the HTML body.
I assume these extra tags could be what's triggering the error.
I'm using Firefox 14.0.1 on WIN7
Hey SevenFactors! Glad to see you're still around.
When you get that error, do you try to post again? Does it eventually go through? If so, could you provide a link to one of the messages?
Also, where in the posting process does the error occur? Is it as soon as you click the "Post" button?
Same deal for you BRIT-KO?
PSX_Cheatster wrote:Hey SevenFactors! Glad to see you're still around.
When you get that error, do you try to post again? Does it eventually go through? If so, could you provide a link to one of the messages?
Also, where in the posting process does the error occur? Is it as soon as you click the "Post" button?
Same deal for you BRIT-KO?
Likewise. From the time when PS community was a community 
---
The error happens after I click the Post button. The error is displayed on its own white webpage. When this happens I just go back one page to find myself back on the Reply To Message page. At this point the text editor is empty. The first time I got the error, I check the thread to see if the posting had gone through and to my surprise it did. Though I get this error my message still get posted on board.
If I remember correctly I got the error when posting these two:
PSX_Cheatster wrote:If you're using a proxy, that could be one cause.
Sometimes, issues like this also occur when the request header is too large (ie. bloated cookies). I'd suggest clearing your browser cookies/cache and see if that helps.
My connection is Internet-Router-PC/Laptop. No proxy servers configuration nor anything. On my laptop I've DNS encryption via DNSCrypt but that is no proxy; anyhow, I get the error on my PC too.
Firefox is set to delete all cookies at end of session. I've gone the extra mile to make sure Firefox truly deletes all cookies. I don't keep cookies longer than they are needed. In my case cookies are not the problem.
Two days ago cleaned the cache, two days later and I've not encountered the problem. Hopefully this is the solution.
-----
I was starting to think that perhaps the constant autosaving by forum platform had to do something with the error.
Support
Corporate
Community
