Eric Covener wrote:
Why both locationmatch AND checking the request URI in setenvif?
The elipsis indicates more stuff, of course. Inside my Location
stanza are access restriction directives to be applied when the
URI matches. I'm hoping (yet another pass on my thread from a
month ago that you made some stabs at answering then, Eric, about
trying to imbed the variable details for a require ldap-group directive
in the URI itself -- there, I said I was going to skip talking about
HOW I'll use the variable extracted, but you MADE me bring it back ;-)
Anyway, that's why both SetEnvIf (to extract the variable value)
and the <Location> stanza (try try to make use of it in authorization
efforts).
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@xxxxxxx
Systems Design Specialist - Lead Phone: (814) 865-4870
Digital Library Technologies FAX: (814) 863-3560
E3 Paterno Library
Penn State University
University Park, PA 16802
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@xxxxxxxxxxxxxxxx
For additional commands, e-mail: users-help@xxxxxxxxxxxxxxxx
|