My opinion is that common sense would dictate trying a little (to a lot) more than the minimum required, esp. if the minimum required didn't work. We did this on the client side but forgot about the server side. I'm not sure there is a real problem here.
However, there *is* a problem to the extent that the error message did not inform us what was really wrong. At a minimum it could have said what size the request was and what size was allowed. In addition, presumably the client side knew it was a server problem and could have said so. A good error message is a lot better than putting it in the documentation and troubleshooting. (I didn't look at either of those for this problem.)
From Ken,
My opinion is that common sense would dictate trying a little (to a lot) more than the minimum required, esp. if the minimum required didn't work. We did this on the client side but forgot about the server side. I'm not sure there is a real problem here.
However, there *is* a problem to the extent that the error message did not inform us what was really wrong. At a minimum it could have said what size the request was and what size was allowed. In addition, presumably the client side knew it was a server problem and could have said so. A good error message is a lot better than putting it in the documentation and troubleshooting. (I didn't look at either of those for this problem.)