PHWinfo banniere

Titres
PORTAIL ANNUAIRE ARTICLES COMPARATEUR HÉBERGEURS DEVIS FORUMS RÉDUCTEUR D'URL
Précédent   PHWinfo > Forums Hébergement > Forum Hébergement serveur > comp.info.servers.win > The incorrect content length problem with Apache, how to stop waiting for data, and send a reply in CGI?
S'inscrire FAQ Membres Recherche Messages du jour Marquer les forums comme lus
comp.info.servers.win Web servers for MS Windows and NT.

The incorrect content length problem with Apache, how to stop waiting for data, and send a reply in CGI?

Réponse
 
LinkBack Outils de la discussion
Vieux 22/09/2005, 15h48   #1 (permalink)
samkipers445r@yahoo.com
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut The incorrect content length problem with Apache, how to stop waiting for data, and send a reply in CGI?

Hello

Maybe someone who knows apache internals can 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 ,
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

  Réponse avec citation
Vieux 22/09/2005, 18h11   #2 (permalink)
Phil Frisbie, Jr.
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: The incorrect content length problem with Apache, how to stopwaiting for data, and send a reply in CGI?

samkipers445r@yahoo.com wrote:

> Hello
>
> Maybe someone who knows apache internals can 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
  Réponse avec citation
Vieux 23/09/2005, 14h08   #3 (permalink)
samkipers445r@yahoo.com
Aucun Avatar
 
Messages: n/a
Hébergeur:
Par défaut Re: The incorrect content length problem with Apache, how to stop waiting for data, and send a reply in CGI?

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

  Réponse avec citation
Réponse


Outils de la discussion

Règles de messages
Vous ne pouvez pas créer de nouvelles discussions
Vous ne pouvez pas envoyer des réponses
Vous ne pouvez pas envoyer des pièces jointes
Vous ne pouvez pas modifier vos messages

Les balises BB sont activées : oui
Les smileys sont activés : oui
La balise [IMG] est activée : oui
Le code HTML peut être employé : non
Trackbacks are oui
Pingbacks are oui
Refbacks are oui


Fuseau horaire GMT +1. Il est actuellement 08h07.


Édité par : vBulletin® version 3.7.2
Copyright ©2000 - 2008, Jelsoft Enterprises Ltd.
Search Engine Friendly URLs by vBSEO 3.2.0 RC5 Tous droits réservés.
Version française #16 par l'association vBulletin francophone
PHWinfo est un site Éducation Sans Frontières
Ad Management by RedTyger
©Tous droits réservés par les parties respectives
Page generated in 0,09124 seconds with 11 queries