https://bz.apache.org/bugzilla/show_bug.cgi?id=58120
Andrew Chadwick <a.t.chadwick@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|PC |All
Keywords| |NeedsReleaseNote,
| |Regression
Summary|ProxyPassInherit does not |ProxyPassInherit affects
|work as expect |ProxyRemote, not ProxyPass
--- Comment #2 from Andrew Chadwick <a.t.chadwick@gmail.com> ---
(In reply to silencer018 from comment #0)
> Is this a bug ? or I misunderstood the usage of this directive ?
Confirmed this in 2.4.52 on Debian 11. You're right about the code:
-------------8<-------------
static const command_rec proxy_cmds[] =
{
// ...
AP_INIT_TAKE2("ProxyRemote", add_proxy_noregex, NULL, RSRC_CONF,
"a scheme, partial URL or '*' and a proxy server"),
AP_INIT_TAKE2("ProxyRemoteMatch", add_proxy_regex, NULL, RSRC_CONF,
"a regex pattern and a proxy server"),
// ...
AP_INIT_RAW_ARGS("ProxyPass", add_pass_noregex, NULL,
RSRC_CONF|ACCESS_CONF,
"a virtual path and a URL"),
AP_INIT_RAW_ARGS("ProxyPassMatch", add_pass_regex, NULL,
RSRC_CONF|ACCESS_CONF,
"a virtual path and a URL"),
// ...
------------->8-------------
Elsewhere, the add_pass*() functions update conf->aliases, and the add_proxy*()
functions update conf->proxies. This directive is preventing or enabling the
inheritance of ProxyRemote and ProxyRemoteMatch, not ProxyPass and
ProxyPassMatch as documented.
I'll attach a test case.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org
Andrew Chadwick <a.t.chadwick@gmail.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
Hardware|PC |All
Keywords| |NeedsReleaseNote,
| |Regression
Summary|ProxyPassInherit does not |ProxyPassInherit affects
|work as expect |ProxyRemote, not ProxyPass
--- Comment #2 from Andrew Chadwick <a.t.chadwick@gmail.com> ---
(In reply to silencer018 from comment #0)
> Is this a bug ? or I misunderstood the usage of this directive ?
Confirmed this in 2.4.52 on Debian 11. You're right about the code:
-------------8<-------------
static const command_rec proxy_cmds[] =
{
// ...
AP_INIT_TAKE2("ProxyRemote", add_proxy_noregex, NULL, RSRC_CONF,
"a scheme, partial URL or '*' and a proxy server"),
AP_INIT_TAKE2("ProxyRemoteMatch", add_proxy_regex, NULL, RSRC_CONF,
"a regex pattern and a proxy server"),
// ...
AP_INIT_RAW_ARGS("ProxyPass", add_pass_noregex, NULL,
RSRC_CONF|ACCESS_CONF,
"a virtual path and a URL"),
AP_INIT_RAW_ARGS("ProxyPassMatch", add_pass_regex, NULL,
RSRC_CONF|ACCESS_CONF,
"a virtual path and a URL"),
// ...
------------->8-------------
Elsewhere, the add_pass*() functions update conf->aliases, and the add_proxy*()
functions update conf->proxies. This directive is preventing or enabling the
inheritance of ProxyRemote and ProxyRemoteMatch, not ProxyPass and
ProxyPassMatch as documented.
I'll attach a test case.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscribe@httpd.apache.org
For additional commands, e-mail: bugs-help@httpd.apache.org