FYI:
wget http://apache.mesi.com.ar//httpd/httpd-2.2.29.tar.gz
--2015-05-15 10:33:31-- http://apache.mesi.com.ar//httpd/httpd-2.2.29.tar.gz
Resolving apache.mesi.com.ar... 2400:cb00:2048:1::681c:1647,
2400:cb00:2048:1::681c:1747, 104.28.23.71, ...
Connecting to apache.mesi.com.ar|2400:cb00:2048:
My bad, I didn't figure out you were talking about 503s from the
backend (as opposed to eg. connect errors which are handled as
internal 503s).
AFAICT recovering from backend error is not reliably feasible, non
idempotent requests (eg. POSTs) cannot be re-sent by a proxy.
On Fri, May 15, 2015 at 1
hhmmm i'm not experiencing that.
i've got a php script on the back end that send a 503 header:
NODE1
NODE2
But when i make requests on the cluster i get 50% of "error" and 50% of
"ok".
2015-05-15 11:09 GMT+02:00 Yann Ylavic :
> Hi,
>
> this is an implicit behaviour.
>
> Regards,
> Yann.
>
Disabling mod_deflate does indeed fix the issue I am seeing, but I wish
to disable compression for just one folder within the virtualhost.
From reading the docs I think I can do this via "SetEnv no-gzip 1"
within the directory in my virtualhost config file.
But after reloading the config file
Hi,
this is an implicit behaviour.
Regards,
Yann.
On Fri, May 15, 2015 at 10:31 AM, nik600 wrote:
> Dear all
>
> is possible to handle the specific http 503 status from a BalancerMember and
> re-forward the request to another member?
>
> Thanks to all in advance
>
> --
> /*/
> nik60
Dear all
is possible to handle the specific http 503 status from a BalancerMember
and re-forward the request to another member?
Thanks to all in advance
--
/*/
nik600
http://www.kumbe.it
