httpd-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From CASTELLE Thomas <>
Subject RE: Apache proxy behaviour...
Date Thu, 02 Feb 2006 16:02:01 GMT
Well, I think increasing the proxy timeout isn't a good idea on a
reverse-proxy in a production environment as it quickly monopolize, when one
of the proxied webservers badly crash, a huge amount of httpd process
waiting for this timeout to occur ...


Anyway, even if the Apache timeout is increased, Firewalls or browsers don't
like idle TCP/IP session either... without speaking of the users ;-)


Regarding my problem, I tried to disable every modules (except mod_proxy of
course), and it still doesn't work...


It seems to confirm what Rüdiger said...



De : [] 
Envoyé : jeudi 2 février 2006 16:48
À :
Cc :
Objet : Re: Apache proxy behaviour...


There is no such thing as an intermediate proxy that has any kind

of 'filtering' going on that won't, on some occasions, need to 'buffer'

some data. I believe even mod_include will 'wait' for tags to resolve

if they split across buffers.


The real questions to ask is...


Why is the proxy timing out? ( I.e. Why isn't it getting the rest of the
data? )


If something is always taking a huge amount of time to come up with

the response then you just need to speed it up or increase your

proxy timeout.



Kevin Kiley


In a message dated 2/2/2006 7:14:01 AM Pacific Standard Time, writes:

Hi there, 

I came with a problem which surprise me, as I thought Apache was working 

We have Apache 2.0.55 working in reverse-proxy in front of different 

One of our website takes a long time to process requests and respond to 
the client. The proxy reaches its timeout and closes the connection. 

So, our developers created a webpage which sends small chunks of data so 
that the connection is never closed. 

I thought it would work as, for me, apache don't wait for the page to be 
complete before sending some chunks to the client... but instead it does 

In our configuration, Apache waits to have the entire page before 
sending it back to the client. Is it because of one of our module ? We 
are using, among other things, mod_rewrite, mod_proxy, mod_deflate, 
mod_security, mod_headers... 

Thanks for your help, 



View raw message