Summary: | BalancerMember enclosed by <If> gives syntax error | ||
---|---|---|---|
Product: | Apache httpd-2 | Reporter: | Spyridon Gouliarmis <spyridon.gouliarmis> |
Component: | mod_proxy | Assignee: | Apache HTTPD Bugs Mailing List <bugs> |
Status: | NEW --- | ||
Severity: | normal | ||
Priority: | P2 | ||
Version: | 2.4.10 | ||
Target Milestone: | --- | ||
Hardware: | PC | ||
OS: | Linux |
Description
Spyridon Gouliarmis
2014-12-04 17:10:35 UTC
(I mean I get the error on Apache startup.) I don't think BalancerMember is designed to be used outside of (plain) Location and <Proxy> configuration sections. Will leave PR open a few days. Confirmed. This is because of: /* * Set a dummy value so that other directives notice that they are inside * a config section. */ cmd->path = "*If"; around line 2485 in core.c This breaks the processing of BalancerMember. What is the goal of this? The original goal was to make a configurable reverse proxy. We figured Apache's configuration could be adapted at launch through environment variables and <If> blocks. We just worked around the issue by building the right Apache configuration in a launcher script and including it whole through an environment variable in Apache's configuration. > What is the goal of this?
Your goal is clear.
My question was not explicit enought.
I meant: "what is the goal of such a behaviour in <if > processing (i.e. cmd->path = "*If";)"
In other words: "could ifsection() be modified to allow the kind of construction you tried to use?"
I just ran into this as well. What is the current status on the issue. |