https://bz.apache.org/bugzilla/show_bug.cgi?id=66374
--- Comment #4 from Michael Orlitzky <mich...@orlitzky.com> ---
I think I'm having the same problem as bug #63146. There seems to be a lot of
magic going on in the config parsing that interacts badly with <If>.
I don't really know what a good solution could look like given that I'm not an
expert on the relevant limitations, but from a dumb user perspective (and to
put it bluntly) it's pretty annoying to have a feature depend on secret
details, and then fail silently / return bullshit / launch missiles when you
run afoul of the rules you didn't know about.
If you asked 100 random programmers or system administrators what
<If "'www' == 'x'">
Error "www and x are equal"
</If>
will do, I would be surprised if any of them guessed right. At a high level, my
complaint is basically just that the actual behavior of <If> should more
closely match the mental model of it that everyone is going to arrive with. And
if that's not possible, throw a sensible error instead of quietly proceeding
with a config that acts nothing like what is written.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: bugs-unsubscr...@httpd.apache.org
For additional commands, e-mail: bugs-h...@httpd.apache.org
