You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by "J.Lance Wilkinson" <jl...@psu.edu> on 2012/03/22 15:18:10 UTC
[users@httpd] SetEnvIf failure or success?
I'm trying to extract part of a URI into an environment variable to use in an
authorization scheme (let's skip talking about how I'll USED that variable for
the moment).
I have the following directives in my configuration:
LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
CustomLog logs/umg.log umgs
...
<Location ~ "^/(.*)/umg/.(.*)(.html|/(.*)?)$">
...
SetEnvIf REQUEST_URI "^/(.*)/umg/.(.*)(.html|/(.*)?)$" UMG=$2
...
</Location>
When I watch that log file, and hit resources that match that location, I'm
seeing entries in the log which suggest a value for the UMG variable is not
being extracted:
xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:13 -0400] "GET
/umgs/umg.up.dlt.sslcerts.mgttool HTTP/1.1" 301 455 UMG=-
xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:25 -0400] "GET
/umgs/umg.up.dlt.ul.gml.managers HTTP/1.1" 301 454 UMG=-
I'd expected to see UMG=up.dlt.sslcerts.mgttool and UMG=up.dlt.ul.gml.managers
on these two log lines.
Several thoughts come to mind:
1) Logging is taking place before the SetEnvIf takes place.
2) Miscoding of Location's regular expression is causing SetEnvIf to be
bypassed.
3) Miscoding of SetEnvIf's regular expression is causing SetEnvIf to fail.
4) Miscoding of SetEnvIf's value specification is causing failure.
Apache 2.2.6, so I don't have the luxury of setting up debug level logging for
mod_setenvif; I also don't have immediate access to the source used for
mod_setenvif so I can't say FOR CERTAIN that it's v2.0.51 or later such that
the $2 in the value specification is legitimate.
Is there anything obvious in these directives that would bear out one of these
suspicions, or would point in a different direction?
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
J.Lance Wilkinson wrote:
> 3) SetEnvIf REQUEST_URI "^(.*)/umg-(.*)$" UMG=$1
>
> Logs (non-matching) REQUEST_URI of "/server-info?config" as:
> ....."GET /server-info?config HTTP/1.1" 200 38314 UMG=-
>
> Logs (matching) REQUEST_URI of
> "/umgs/umg-up.dlt.ul.gml.managers/umgs.php" as:
> ....."GET /umgs/umg-up.dlt.ul.gml.managers/umgs.php HTTP/1.1" 401 1837
> UMG=/errorpages/401.html
>
> I have to wonder if it's not the parsing, but the assignment that's
> failing, that version 2.0.15 thing -- that my Solaris 10 version of the
> code is old...
Nope, assignment is happening correctly.
Problem was that I still had my <Location/> stanza active which
actually tries to USE the extracted variable in a require ldap-group
directive. And clearly that part doesn't work (yet).
The following directives, when there's no <Location/> stanza matching
the same REQUEST_URI, does indeed extract the desired content:
LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
CustomLog logs/umg.log umgs
...
SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG=$2
Logs (non-matching) REQUEST_URI of "/liasprobe/helpalert" as:
....."GET /liasprobe/helpalert HTTP/1.1" 200 425 UMG=-
Logs (matching) REQUEST_URI of "/umgs/umg-up.dlt.ul.gml.managers/umgs.php" as:
....."G"GET /umgs/umg-up.dlt.ul.gml.managers/umgs.php HTTP/1.1" 200 56920
UMG=up.dlt.ul.gml.managers
The previously noted UMG=/errorpages/401.html was apparently due to
authentication failure (401) on the previously included <Location/> stanza that
tried to use the value of UMG in a 'require ldap-group' directive
("require ldap-group cn=umg/${UMG},dc=someorg,dc=somedomain")
being rewritten (?) thru an ErrorDocument directive to a different URI, which
apparently re-parsed in SetEnvIf ???
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
Mysterious Mose wrote:
> Hello again Lance,
>
>> PCRE version 7.8 2008-09-05
>> re> @^/(.*)/umg-(.*)(.html|/(.*)?)$@
>> data> /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
>> 0: /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
>> 1: umgs
>> 2: up.dlt.sslcerts.mgttool
>> 3: /umgs.php
>> 4: umgs.ph
>
> Wow, this is a very handy tool I have never heard of before! Thanks
> for mentioning it, I'm sure it will be handy for me to use in the
> future.
Can't take credit for this, Eric Covener noted it in this thread
first. Not available on my Solaris 10 platforms, but was present on
an RHEL6 host I'm eventually going to be migrating those Solaris 10
-hosted sites to them. I also found web-based cgi scripts that do
similar analysis.
>
>> SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG="arbitrary"
>>
>> And I still see the same empty results (UMG=- logged).
>>
>> This suggests the SetEnvIf pattern match is failing, because otherwise I
>> SHOULD
>> be getting a value of "arbitrary" assigned, right?
>
> A brute force way to debug this would be to temporarily try:
>
> SetEnvIf REQUEST_URI "^(.*)$" UMG=$1
>
> Or even something simpler like:
>
> SetEnvIf REQUEST_URI "." UMG="arbitrary"
>
> Then see what you get. If still nothing, it's apparently not even
> testing this condition. If you get what you expect, then gradually
> build up to the regexp you want, and see at what point you stop
> getting data.
Well, that was an interesting exercise...
1) SetEnvIf REQUEST_URI "^(.*)$" UMG=1
Logs (matching) REQUEST_URI of "/umgs/umg-up.dlt.ul.gml.managers/umgs.php" as:
....."GET /umgs/umg-up.dlt.ul.gml.managers/umgs.php HTTP/1.1" 401 1837 UMG=1
2) SetEnvIf REQUEST_URI "^(.*)$" UMG=$1
Logs (non-matching) REQUEST_URI of "/liasprobe/helpalert" as:
....."GET /liasprobe/helpalert HTTP/1.1" 200 424 UMG=/liasprobe/helpalert
Logs (matching) REQUEST_URI of "/umgs/umg-up.dlt.ul.gml.managers/umgs.php" as:
....."GET /umgs/umg-up.dlt.ul.gml.managers/umgs.php HTTP/1.1" 401 1837
UMG=/errorpages/401.html
3) SetEnvIf REQUEST_URI "^(.*)/umg-(.*)$" UMG=$1
Logs (non-matching) REQUEST_URI of "/server-info?config" as:
....."GET /server-info?config HTTP/1.1" 200 38314 UMG=-
Logs (matching) REQUEST_URI of "/umgs/umg-up.dlt.ul.gml.managers/umgs.php" as:
....."GET /umgs/umg-up.dlt.ul.gml.managers/umgs.php HTTP/1.1" 401 1837
UMG=/errorpages/401.html
I have to wonder if it's not the parsing, but the assignment that's failing,
that version 2.0.15 thing -- that my Solaris 10 version of the code is old...
Aside -- shouldn't there be a way I can examine the mod_setenvif.so file to
determine which version it is? mod_info's server-info handler clearly isn't
giving it to me.
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by Mysterious Mose <we...@drdemento.com>.
Hello again Lance,
> PCRE version 7.8 2008-09-05
> re> @^/(.*)/umg-(.*)(.html|/(.*)?)$@
> data> /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
> 0: /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
> 1: umgs
> 2: up.dlt.sslcerts.mgttool
> 3: /umgs.php
> 4: umgs.ph
Wow, this is a very handy tool I have never heard of before! Thanks
for mentioning it, I'm sure it will be handy for me to use in the
future.
> SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG="arbitrary"
>
> And I still see the same empty results (UMG=- logged).
>
> This suggests the SetEnvIf pattern match is failing, because otherwise I
> SHOULD
> be getting a value of "arbitrary" assigned, right?
A brute force way to debug this would be to temporarily try:
SetEnvIf REQUEST_URI "^(.*)$" UMG=$1
Or even something simpler like:
SetEnvIf REQUEST_URI "." UMG="arbitrary"
Then see what you get. If still nothing, it's apparently not even
testing this condition. If you get what you expect, then gradually
build up to the regexp you want, and see at what point you stop
getting data.
MM
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
Eric Covener wrote:
> On Thu, Mar 22, 2012 at 10:18 AM, J.Lance Wilkinson <jl...@psu.edu> wrote:
>> I'm trying to extract part of a URI into an environment variable to use in
>> an authorization scheme (let's skip talking about how I'll USED that
>> variable for the moment).
>>
>> I have the following directives in my configuration:
>>
>> LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
>> CustomLog logs/umg.log umgs
>> ...
>> <Location ~ "^/(.*)/umg/.(.*)(.html|/(.*)?)$">
>> ...
>> SetEnvIf REQUEST_URI "^/(.*)/umg/.(.*)(.html|/(.*)?)$" UMG=$2
>> ...
>> </Location>
>>
>> When I watch that log file, and hit resources that match that location, I'm
>> seeing entries in the log which suggest a value for the UMG variable is not
>> being extracted:
>>
>> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:13 -0400] "GET
>> /umgs/umg.up.dlt.sslcerts.mgttool HTTP/1.1" 301 455 UMG=-
>> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:25 -0400] "GET
>> /umgs/umg.up.dlt.ul.gml.managers HTTP/1.1" 301 454 UMG=-
>>
>> I'd expected to see UMG=up.dlt.sslcerts.mgttool and
>> UMG=up.dlt.ul.gml.managers on these two log lines.
>>
>> Several thoughts come to mind:
>> 1) Logging is taking place before the SetEnvIf takes place.
>
> definitely not
That's good to be certain of...
>
>> 2) Miscoding of Location's regular expression is causing SetEnvIf to be
>> bypassed.
>
> easy to test, locationmatch not needed if you're already comparing
> against the URI in the setenvif.
I moved the SetEnvIf outside the <Location/> stanza. No change.
>
>> 3) Miscoding of SetEnvIf's regular expression is causing SetEnvIf to fail.
>
> likely, the "pcretest" program says it doesn't match.
I changed my regular expression to read
@^/(.*)/umg-(.*)(.html|/(.*)?)$@
(I can get away with this now, during development.)
Thus I would want to match URIs like:
/umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
By changing the period to a hyphen it eliminates the whole
escaping thing I was doing with /. that I should have been
doing with \. or just . that Mysterious Mose <we...@drdemento.com>
caught earlier.
> This string would need either a .html or another / to match, right?
>
> @^/(.*)/umg/.(.*)(.html|/(.*)?)$@
> /umgs
> /umg.up.dlt.sslcerts.mgttool (never found .html or /)
>
> Maybe you meant the ? to apply to the entire alternation and not the .*?
I do. It should never receive anything without either
a .html or a trailing / (and probably other content) but I guess
that's a separate excercise since I see without one of them the
matching fails.
>> 4) Miscoding of SetEnvIf's value specification is causing failure.
>
> easy to test w/ a literal value, not likely the case though.
>
$ pcretest
PCRE version 7.8 2008-09-05
re> @^/(.*)/umg-(.*)(.html|/(.*)?)$@
data> /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
0: /umgs/umg-up.dlt.sslcerts.mgttool/umgs.php
1: umgs
2: up.dlt.sslcerts.mgttool
3: /umgs.php
4: umgs.ph
data> /long/arbitrary/prefix/umg-ul.dlt.ul.gml.managers/
0: /long/arbitrary/prefix/umg-ul.dlt.ul.gml.managers/
1: long/arbitrary/prefix
2: ul.dlt.ul.gml.managers
3: /
4:
data> /long/arbitrary/prefix/umg-up.dlt.spamfratch.society/membership.report
0: /long/arbitrary/prefix/umg-up.dlt.spamfratch.society/membership.report
1: long/arbitrary/prefix
2: up.dlt.spamfratch.society
3: /membership.report
4: membership.report
data>
So, I want the UMG variable to match the #2 result.
Transcribing these values into my config
...
LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
CustomLog logs/umg.log umgs
...
SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG=$2
I still see no value for the UMG variable, suggesting that it's still a
regular expression issue OR miscoding of the value specification (or
UMG)
xxx.xxx.xxx.xxx - - [22/Mar/2012:11:36:06 -0400] "GET
/umgs/umg-up.dlt.sslcerts.mgttool/umgs.php HTTP/1.1" 401 1837 UMG=-
So I change my SetEnvIf directive to specify an explict value for UMG
to be equal to, I still see UMG=- in the log:
SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG=arbitrary
And I still see the same empty results (UMG=- logged).
I try enclosing the assigned value as a text string:
SetEnvIf REQUEST_URI "^/(.*)/umg-(.*)(.html|/(.*)?)$" UMG="arbitrary"
And I still see the same empty results (UMG=- logged).
This suggests the SetEnvIf pattern match is failing, because otherwise I SHOULD
be getting a value of "arbitrary" assigned, right?
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
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@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by Eric Covener <co...@gmail.com>.
On Thu, Mar 22, 2012 at 10:18 AM, J.Lance Wilkinson <jl...@psu.edu> wrote:
> I'm trying to extract part of a URI into an environment variable to use in
> an authorization scheme (let's skip talking about how I'll USED that
> variable for the moment).
>
> I have the following directives in my configuration:
>
> LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
> CustomLog logs/umg.log umgs
> ...
> <Location ~ "^/(.*)/umg/.(.*)(.html|/(.*)?)$">
> ...
> SetEnvIf REQUEST_URI "^/(.*)/umg/.(.*)(.html|/(.*)?)$" UMG=$2
> ...
> </Location>
>
Why both locationmatch AND checking the request URI in setenvif?
> When I watch that log file, and hit resources that match that location, I'm
> seeing entries in the log which suggest a value for the UMG variable is not
> being extracted:
>
> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:13 -0400] "GET
> /umgs/umg.up.dlt.sslcerts.mgttool HTTP/1.1" 301 455 UMG=-
> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:25 -0400] "GET
> /umgs/umg.up.dlt.ul.gml.managers HTTP/1.1" 301 454 UMG=-
>
> I'd expected to see UMG=up.dlt.sslcerts.mgttool and
> UMG=up.dlt.ul.gml.managers on these two log lines.
>
> Several thoughts come to mind:
> 1) Logging is taking place before the SetEnvIf takes place.
definitely not
> 2) Miscoding of Location's regular expression is causing SetEnvIf to be
> bypassed.
easy to test, locationmatch not needed if you're already comparing
against the URI in the setenvif.
> 3) Miscoding of SetEnvIf's regular expression is causing SetEnvIf to fail.
likely, the "pcretest" program says it doesn't match.
This string would need either a .html or another / to match, right?
@^/(.*)/umg/.(.*)(.html|/(.*)?)$@
/umgs
/umg.up.dlt.sslcerts.mgttool (never found .html or /)
Maybe you meant the ? to apply to the entire alternation and not the .*?
> 4) Miscoding of SetEnvIf's value specification is causing failure.
easy to test w/ a literal value, not likely the case though.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by "J.Lance Wilkinson" <jl...@psu.edu>.
Mysterious Mose wrote:
> Good morning Lance,
>
> I don't think your regexp is quite right. You could test it out with
> grep or sed or something by echoing in the string from the log.
>
> You have:
>
> "^/(.*)/umg/.(.*)(.html|/(.*)?)$"
>
> I think you mean:
>
> "^/(.*)/umg\.(.*)(.html|/(.*)?)$"
>
> That is, I believe you want to backslash the period after umg to treat
> it as a literal, rather than having a forward slash which is not in
> your example strings.
Aha... I HATE regular expressions. Well, I've lots of other rewrite
rules in the same configurations where .html matches so do I need to
escape the "." after "umg" at all, I wonder.
>
> I'm not completely sure about the (.html|/(.*)?) part because I'm not
> sure what you're trying to do there. I'm wondering if you mean to have
> the question mark outside of the outer parentheses, but it may be
> perfectly correct as you have it, I just don't know.
I want to treat
{optional superordinate}umg.{something matches}.html
and
{optional superordinate }umg.{something matches}/{subordinate} to the
same handling restrictions. I use this kind of pattern in a lot of
other restriction impositions in my server.
--
J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
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@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org
Re: [users@httpd] SetEnvIf failure or success?
Posted by Mysterious Mose <we...@drdemento.com>.
Good morning Lance,
I don't think your regexp is quite right. You could test it out with
grep or sed or something by echoing in the string from the log.
You have:
"^/(.*)/umg/.(.*)(.html|/(.*)?)$"
I think you mean:
"^/(.*)/umg\.(.*)(.html|/(.*)?)$"
That is, I believe you want to backslash the period after umg to treat
it as a literal, rather than having a forward slash which is not in
your example strings.
I'm not completely sure about the (.html|/(.*)?) part because I'm not
sure what you're trying to do there. I'm wondering if you mean to have
the question mark outside of the outer parentheses, but it may be
perfectly correct as you have it, I just don't know.
But at least you need to make the one change, and see what happens.
> I'm trying to extract part of a URI into an environment variable to use in
> an
> authorization scheme (let's skip talking about how I'll USED that variable
> for
> the moment).
>
> I have the following directives in my configuration:
>
> LogFormat "%h %l %u %t \"%r\" %>s %b UMG=%{UMG}e" umgs
> CustomLog logs/umg.log umgs
> ...
> <Location ~ "^/(.*)/umg/.(.*)(.html|/(.*)?)$">
> ...
> SetEnvIf REQUEST_URI "^/(.*)/umg/.(.*)(.html|/(.*)?)$" UMG=$2
> ...
> </Location>
>
> When I watch that log file, and hit resources that match that location,
> I'm
> seeing entries in the log which suggest a value for the UMG variable is
> not
> being extracted:
>
> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:13 -0400] "GET
> /umgs/umg.up.dlt.sslcerts.mgttool HTTP/1.1" 301 455 UMG=-
> xxx.xxx.xxx.xxx - jlw12 [22/Mar/2012:09:31:25 -0400] "GET
> /umgs/umg.up.dlt.ul.gml.managers HTTP/1.1" 301 454 UMG=-
>
> I'd expected to see UMG=up.dlt.sslcerts.mgttool and
> UMG=up.dlt.ul.gml.managers
> on these two log lines.
>
> Several thoughts come to mind:
> 1) Logging is taking place before the SetEnvIf takes place.
> 2) Miscoding of Location's regular expression is causing SetEnvIf to be
> bypassed.
> 3) Miscoding of SetEnvIf's regular expression is causing SetEnvIf to fail.
> 4) Miscoding of SetEnvIf's value specification is causing failure.
>
> Apache 2.2.6, so I don't have the luxury of setting up debug level logging
> for
> mod_setenvif; I also don't have immediate access to the source used for
> mod_setenvif so I can't say FOR CERTAIN that it's v2.0.51 or later such
> that
> the $2 in the value specification is legitimate.
>
> Is there anything obvious in these directives that would bear out one of
> these
> suspicions, or would point in a different direction?
>
> --
> J.Lance Wilkinson ("Lance") InterNet: Lance.Wilkinson@psu.edu
> 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@httpd.apache.org
> For additional commands, e-mail: users-help@httpd.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org