You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by dE <de...@gmail.com> on 2016/07/15 13:27:07 UTC
[users@httpd] mod_proxy nofailover parameter.
Hi,
What I understand of nofailover is that in case a client is
fetching from this proxy and the origin server goes to an error or
disabled state, a reset packet won't be sent to the client, instead the
backend will be changed and the client will continue the operation
uninterrupted.
But this does not appear to be happening with HTTP.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] mod_proxy nofailover parameter.
Posted by dE <de...@gmail.com>.
I'll come back to this later.
On 07/15/16 22:25, Daniel wrote:
>
> Failover is what you described, nofailover is for the opposite
>
> El 15 jul. 2016 3:27 p. m., "dE" <de.techno@gmail.com
> <ma...@gmail.com>> escribi�:
>
> Hi,
>
> What I understand of nofailover is that in case a client is
> fetching from this proxy and the origin server goes to an error or
> disabled state, a reset packet won't be sent to the client,
> instead the backend will be changed and the client will continue
> the operation uninterrupted.
>
> But this does not appear to be happening with HTTP.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> <ma...@httpd.apache.org>
> For additional commands, e-mail: users-help@httpd.apache.org
> <ma...@httpd.apache.org>
>
Re: [users@httpd] mod_proxy nofailover parameter.
Posted by Daniel <df...@gmail.com>.
Failover is what you described, nofailover is for the opposite
El 15 jul. 2016 3:27 p. m., "dE" <de...@gmail.com> escribió:
> Hi,
>
> What I understand of nofailover is that in case a client is fetching
> from this proxy and the origin server goes to an error or disabled state, a
> reset packet won't be sent to the client, instead the backend will be
> changed and the client will continue the operation uninterrupted.
>
> But this does not appear to be happening with HTTP.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>