<html>
<head>
<meta content="text/html; charset=windows-1252"
http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<p><br>
</p>
<br>
<div class="moz-cite-prefix">On 4/17/17 2:19 PM, Cantor, Scott
wrote:<br>
</div>
<br>
<br>
<blockquote cite="mid:1C8FF7C8-4AD8-48CB-A450-19E17EF2DE44@osu.edu"
type="cite">
<pre wrap="">
I assume that parsing some kind of environment expression would have to be done by every module, and wouldn't be a generic feature. If that's not the case (and the docs sort of imply maybe it is generic),</pre>
</blockquote>
<br>
They do sort of imply that it might be generic, which was why I was
asking, but...<br>
<br>
<blockquote cite="mid:1C8FF7C8-4AD8-48CB-A450-19E17EF2DE44@osu.edu"
type="cite">
<pre wrap=""> then I have no idea what might or might not work, all my module does is consume the parameter as a value to match.</pre>
</blockquote>
<br>
...here [1], which is linked from that LocationMatch section, they
also sort of imply you have to use the new apparently standardized
"ap_expr expression parser". So who the hell knows.<br>
<br>
The OP said he was trying the match group and it wasn't working, so
unless he's making a mistake and/or pending confirmation of the
httpd version, sounds like it maybe doesn't currently work.<br>
<br>
So maybe an RFE is in order? Don't imagine is a super huge
priority, but would be a neat feature. I was thinking would be nice
for example for user-specific spaces, like
"/users/<username>", without having to statically declare all
the authZ rules, for each user.<br>
<br>
<br>
[1] <a class="moz-txt-link-freetext" href="http://httpd.apache.org/docs/2.4/expr.html">http://httpd.apache.org/docs/2.4/expr.html</a><br>
<br>
<br>
<br>
</body>
</html>