So, do we have any conclusion? Should I make modifications and post patch?
--
Marko Kevac
On Jun 4, 2009, at 4:16 AM, Kevac Marko wrote:
So, do we have any conclusion? Should I make modifications and post
patch?
Sure... no guarantees that they'll be applied, but it would
be useful to see what you have in mind.
On Thu, Jun 4, 2009 at 4:32 PM, Jim Jagielski j...@jagunet.com wrote:
Sure... no guarantees that they'll be applied, but it would
be useful to see what you have in mind.
Huh. I thought it would be easy as fixing just mod_proxy.c, but...
It occurred that mod_proxy_http thinks that, for example,
Hello.
I am using mod_proxy and mod_proxy_balancer for proxying requests to
group of workers.
Recentry I have stumbled upon issues with failover retries when worker
returns error.
For example I have balancer with 10 equal workers. One of them breaks
and for 1 of 10 requests return
2009 13:27
An: dev@httpd.apache.org
Cc: denn nevera
Betreff: mod_proxy. mod_proxy_balancer and failovers
Hello.
I am using mod_proxy and mod_proxy_balancer for proxying requests to
group of workers.
Recentry I have stumbled upon issues with failover retries when worker
returns error
On Tue, Jun 2, 2009 at 3:49 PM, Plüm, Rüdiger, VF-Group
ruediger.pl...@vodafone.com wrote:
A 404 is no error regarding balancing and a proper HTTP response by the
backend.
You need to send back a HTTP_INTERNAL_ERROR or a HTTP_SERVICE_UNAVAILABLE in
this
case but without any error page.
Who
On Tue, Jun 2, 2009 at 3:49 PM, Plüm, Rüdiger, VF-Group
ruediger.pl...@vodafone.com wrote:
A 404 is no error regarding balancing and a proper HTTP response by the
backend.
You need to send back a HTTP_INTERNAL_ERROR or a HTTP_SERVICE_UNAVAILABLE in
this
case but without any error page.
On 2 Jun 2009, at 13:05, Kevac Marko wrote:
On Tue, Jun 2, 2009 at 3:49 PM, Plüm, Rüdiger, VF-Group
ruediger.pl...@vodafone.com wrote:
A 404 is no error regarding balancing and a proper HTTP response
by the backend.
You need to send back a HTTP_INTERNAL_ERROR or a
HTTP_SERVICE_UNAVAILABLE
On Tue, Jun 2, 2009 at 4:15 PM, Nick Kew n...@webthing.com wrote:
How is the balancer supposed to know that one valid HTTP response
is an error while another is correct? A 404 or other error response
doesn't mean there's a problem with the server!
These HTTP responses can be configured in
On Tue, Jun 2, 2009 at 4:15 PM, Nick Kew n...@webthing.com wrote:
How is the balancer supposed to know that one valid HTTP response
is an error while another is correct? A 404 or other error response
doesn't mean there's a problem with the server!
Sorry, didn't fully understood your question.
On Jun 2, 2009, at 9:24 AM, Kevac Marko wrote:
On Tue, Jun 2, 2009 at 4:15 PM, Nick Kew n...@webthing.com wrote:
How is the balancer supposed to know that one valid HTTP response
is an error while another is correct? A 404 or other error response
doesn't mean there's a problem with the
On 02.06.2009 15:24, Kevac Marko wrote:
On Tue, Jun 2, 2009 at 4:15 PM, Nick Kew n...@webthing.com wrote:
How is the balancer supposed to know that one valid HTTP response
is an error while another is correct? A 404 or other error response
doesn't mean there's a problem with the server!
On Tue, Jun 2, 2009 at 6:08 PM, Rainer Jung rainer.j...@kippdata.de wrote:
You have chosen an especially problematic example. If a not found
triggers error status for the worker, then you will have continuous
denial of service.
Nearly every productive web server I know of, has every now and
13 matches
Mail list logo
