This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal


~Manny Bubrezenettu
Feb 25, 2014, 4:50 PM
2 Posts

HTTP Web Server: Invalid Post Request - too little data

  • Category: Domino Server
  • Platform: Windows
  • Release: 9.0.1
  • Role: Administrator,Developer
  • Tags:
  • Replies: 2

Every now and then we see an "Invalid Post Request Exception" generated by the Domino HTTP Web Server in the console log.  After upgrading to Domino Server 9.0.1, an additional piece of information is included in the console log for these messages.  Included in the message is (__) which means "too little data" per SPR #MKIN8YJSUF.

Can someone provide some pointers that would help us determine the root cause of this error?  Are there any Domino traces that can be turned on to provide more information? From the web log, we can see that a "500" error is being generated back to the user's browser indicating an internal error. 

Is there a way to easily generate this error in a test environment?

A lot of web traffic goes through this production server, and only a small number of errors are generated.  We would like to resolve the issue, though, so that our external users will not lose any data from the POST request.

~Arnold Frofreeburoni
Feb 25, 2014, 8:01 PM
27 Posts
Post data error
The root cause of the error is that the Web Server did not receive all the post data from the client.  If the POST specified a content length of 1000 bytes, the Web Server will print this error if it does not receive a 1000 bytes of post data. This can happen for an number of reasons, but most of the time the error is caused by the network connection dropping or  the server not receiving the data in a timely fashion and not receiving any data within the input time-out specified in the NAB.

A simple way to reproduce is to upload a medium to large file then hit the Browser Stop button or close the Browser before upload finishes.  

If mobile devices are in use it may be the case that the device lost connectivity for a brief time and the connection timed out

If one needs to get to the root cause why we see this error it may be necessary to get network traces of the connections to see what is happening on the wire.  One will have to isolate the transaction to understand what happened to the underlying tcp connection.

One could increase the default input time-out from 15 seconds to 30 seconds or more to see if it helps, but it may be the case that users hit the stop button before the all data was delivered to the network.

This forum is closed to new posts and responses. Individual names altered for privacy purposes. The information contained in this website is provided for informational purposes only and should not be construed as a forum for customer support requests. Any customer support requests should be directed to the official HCL customer support channels below:

HCL Software Customer Support Portal for U.S. Federal Government clients
HCL Software Customer Support Portal