This is a discussion on The incorrect content length problem with Apache, how to stop waiting for data, and send a reply in CGI? within the Windows Web Servers forums, part of the Web Server and Related Forums category; Hello Maybe someone who knows apache internals can help on this issue. We created an http client application, and a ...
|
|||||||
| FAQ | Members List | Calendar | Search | Today's Posts | Mark Forums Read |
|
|||
|
Hello
Maybe someone who knows apache internals can help on this issue. We created an http client application, and a server CGI script on C++ to exchange data between the application which is spread among many users and our server. Unfortunately the client application had a bug with https POST method when it sent less data than specified in content length header. It happens on a certain combination of input data entered by end user. As the result the Apache server waits for the missing data because of incorrect content length sent by the client, and we never have a chance to send a reply back to the client application. The client application simply closes the connection after one minute timeout period. Is there any way to force Apache to cancel the wait on receiving missing data in Post method and switch it to sending data to reply back to the client application from CGI script? We tried writing to stdout and/or closing stdin, but it doesn't help, it seems that Apache keeps on hanging, and doesn't want to send anything while waiting for the missing data because of incorrent content length. Thanks, Sam Kipers |
|
|||
|
samkipers445r@yahoo.com wrote:
> Hello > > Maybe someone who knows apache internals can help on this issue. > > We created an http client application, and a server CGI script on C++ > to exchange data between the application which is spread among many > users and our server. Unfortunately the client application had a bug > with https POST method when it sent less data than specified in content > length header. It happens on a certain combination of input data > entered by end user. As the result the Apache server waits for the > missing data because of incorrect content length sent by the client, > and we never have a chance to send a reply back to the client > application. The client application simply closes the connection after > one minute timeout period. > > Is there any way to force Apache to cancel the wait on receiving > missing data in Post method and switch it to sending data to reply back > to the client application from CGI script? Am I missing something? It seems to me you are asking to tweak Apache in order to 'correct' a programming problem with your client. Why not simply fix your client so that it never sends "less data than specified in content length header"? -- Phil Frisbie, Jr. Hawk Software http://www.hawksoft.com |
|
|||
|
Hello Phil,
The bug in the client has been fixed already. We cannot update the client among our clients quickly. Usually it takes 2-3 months. Thus the problem still persists. The server is overloaded with idle script processes. Is there a way to fix the problem programmatically with CGI? Somehow we need to tell Apache to stop waiting for data and send a required reply to the client. I feel that customizing/patching Apache for this particular problem is not a good decision. Any suggestions? Thanks, Sam Kipers |