[JBoss JIRA] (MODCLUSTER-505) ProxyErrorOverride=On causes workers in error state after 500 errors
by Michal Karm Babacek (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-505?page=com.atlassian.jira.pl... ]
Michal Karm Babacek closed MODCLUSTER-505.
------------------------------------------
> ProxyErrorOverride=On causes workers in error state after 500 errors
> ---------------------------------------------------------------------
>
> Key: MODCLUSTER-505
> URL: https://issues.jboss.org/browse/MODCLUSTER-505
> Project: mod_cluster
> Issue Type: Bug
> Components: Native (httpd modules)
> Affects Versions: 1.3.2.Final, 1.2.12.Final
> Reporter: Aaron Ogburn
> Assignee: Jean-Frederic Clere
> Fix For: 1.2.14.Final, 1.3.5.Final
>
>
> When a VirtualHost uses ProxyPass to proxy traffic to the backend and uses ProxyErrorOverride to host custom error pages on Apache httpd side, when the backend replies with a 50x error code mod_proxy/mod_cluster marks that worker as down, breaking session stickiness. This behaviour is quite similar to have failonstatus=500 for example.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (MODCLUSTER-549) mod_proxy_cluster should display the full version string of httpd it was built with
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-549?page=com.atlassian.jira.pl... ]
Radoslav Husar edited comment on MODCLUSTER-549 at 11/1/16 10:07 AM:
---------------------------------------------------------------------
I think this is a good idea in general. (I would prefer to use a different format than delimited by underscore as the version name just gets too long, e.g. something like "mod_cluster/1.2.3.Final build against 2.2.50...").
was (Author: rhusar):
I think this is a good idea in general. (I would prefer to use a different format than delimited by underscore as the version name just gets too long.)
> mod_proxy_cluster should display the full version string of httpd it was built with
> -----------------------------------------------------------------------------------
>
> Key: MODCLUSTER-549
> URL: https://issues.jboss.org/browse/MODCLUSTER-549
> Project: mod_cluster
> Issue Type: Enhancement
> Components: Native (httpd modules)
> Affects Versions: 1.2.13.Final, 1.3.5.Final
> Reporter: Michal Karm Babacek
> Assignee: Michal Karm Babacek
>
> This is a suggestion to display: {code}
> [Tue Oct 25 12:48:18 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_cluster/1.2.13.Final_httpd-2.2.15-39.el6.x86_64 configured -- resuming normal operations
> {code} instead of the current version string {code}
> [Mon Oct 31 06:31:31 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_cluster/1.2.13.Final configured -- resuming normal operations
> {code}
> The motivation is to clearly state with which httpd it is safe to to run mod_proxy_cluster modules so as to avoid mysterious SegFaults caused by "I took these mod_proxy_cluster modules build with httpd x and run them with httpd y and it all seemed to be good up until...".
> I'm not absolutely sure this is the right place to do so though. I'd like to hear from [~rhusar] and [~jfclere] to either upvote this enhancement or to downvote it into oblivion.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months
[JBoss JIRA] (MODCLUSTER-549) mod_proxy_cluster should display the full version string of httpd it was built with
by Radoslav Husar (JIRA)
[ https://issues.jboss.org/browse/MODCLUSTER-549?page=com.atlassian.jira.pl... ]
Radoslav Husar commented on MODCLUSTER-549:
-------------------------------------------
I think this is a good idea in general. (I would prefer to use a different format than delimited by underscore as the version name just gets too long.)
> mod_proxy_cluster should display the full version string of httpd it was built with
> -----------------------------------------------------------------------------------
>
> Key: MODCLUSTER-549
> URL: https://issues.jboss.org/browse/MODCLUSTER-549
> Project: mod_cluster
> Issue Type: Enhancement
> Components: Native (httpd modules)
> Affects Versions: 1.2.13.Final, 1.3.5.Final
> Reporter: Michal Karm Babacek
> Assignee: Michal Karm Babacek
>
> This is a suggestion to display: {code}
> [Tue Oct 25 12:48:18 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_cluster/1.2.13.Final_httpd-2.2.15-39.el6.x86_64 configured -- resuming normal operations
> {code} instead of the current version string {code}
> [Mon Oct 31 06:31:31 2016] [notice] Apache/2.2.15 (Unix) DAV/2 mod_cluster/1.2.13.Final configured -- resuming normal operations
> {code}
> The motivation is to clearly state with which httpd it is safe to to run mod_proxy_cluster modules so as to avoid mysterious SegFaults caused by "I took these mod_proxy_cluster modules build with httpd x and run them with httpd y and it all seemed to be good up until...".
> I'm not absolutely sure this is the right place to do so though. I'd like to hear from [~rhusar] and [~jfclere] to either upvote this enhancement or to downvote it into oblivion.
--
This message was sent by Atlassian JIRA
(v7.2.2#72004)
7 years, 5 months