AW: Apache proxy behaviour...
-Ursprüngliche Nachricht- Von: CASTELLE Thomas . > 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... In general mod_proxy_http of httpd 2.2.x is prepared for this task, but is does not work because of the EAGAIN problem. mod_proxy_http of httpd 2.0.x is not prepared at all for such things. Regards Rüdiger
RE: Apache proxy behaviour...
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 : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : jeudi 2 février 2006 16:48 À : dev@httpd.apache.org Cc : [EMAIL PROTECTED] 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. Yours... Kevin Kiley In a message dated 2/2/2006 7:14:01 AM Pacific Standard Time, [EMAIL PROTECTED] writes: Hi there, I came with a problem which surprise me, as I thought Apache was working differently... We have Apache 2.0.55 working in reverse-proxy in front of different webservers. 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, Regards, Thomas.
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. Yours... Kevin Kiley In a message dated 2/2/2006 7:14:01 AM Pacific Standard Time, [EMAIL PROTECTED] writes: Hi there, I came with a problem which surprise me, as I thought Apache was working differently... We have Apache 2.0.55 working in reverse-proxy in front of different webservers. 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, Regards, Thomas.
AW: Apache proxy behaviour...
> -Ursprüngliche Nachricht- > Von: Matthieu Estrade > > The reverse proxy read a brigade, then forward it to the > client. It should not > buffer the response but forward block of data. Maybe it's > because of deflate mod_deflate buffers definitely. You need to turn it off for such pages or you need to write a lot of garabage data to make it flush. > or mod_security... Maybe if you check the outgoing responses. If not I would say no. > > But this behaviour is not normal imho. It is :-(. This has something to do with the improper returning of the EAGAIN status code in the filter chain. BTW: It currently works with mod_proxy_ajp in httpd 2.2.x, but not with mod_proxy_http. Regards Rüdiger
Re: Apache proxy behaviour...
The reverse proxy read a brigade, then forward it to the client. It should not buffer the response but forward block of data. Maybe it's because of deflate or mod_security... But this behaviour is not normal imho. Matthieu On Thursday 02 February 2006 16:13, CASTELLE Thomas wrote: > Hi there, > > I came with a problem which surprise me, as I thought Apache was working > differently... > > We have Apache 2.0.55 working in reverse-proxy in front of different > webservers. > > 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, > > Regards, > > Thomas.
Apache proxy behaviour...
Title: Apache proxy behaviour... Hi there, I came with a problem which surprise me, as I thought Apache was working differently... We have Apache 2.0.55 working in reverse-proxy in front of different webservers. 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, Regards, Thomas.
