The httpd.conf man page uses the term "request path", which I assumed when
reading
the man page would be the full "http://company.com/web/page";, but I found
through
experimentation that it would be "/web/page".
The httpd.conf man page says that for the "location" directive
" The path argument will be matched against the "request path" with shell
globbing rules".
I eventually figured that this was not true. Shell gobbing does not allow '*'
to match any '/'
httpd's globbing does match '/'. I did not experiment to find out how it treats
a leading '.',
or '{' and '}'.
I thought the "location" directive was going to be awkward to use, but
eventually I realized
that every "location" directive that match the "request path" would be applied,
and the
rules would be accumulated for that "request path"
The man page makes no reference of what happens will overlapping "location"
directives,
I think it should. I assume that if there are conflicting rules with in the
"location" directives
the last one wins. I don't know, but also I did not experiment with a rule not
within a
"location" directive that conflicts and follows a rule within a "location"
directive.
The "block" directive allows an optional "uri". Which would mean you would
expect to
start with "http://"; or something similar. The "block" does, as in the
examples, work
with that syntax, but it also accepts a "request path", simplifying simple
redirection.
I had a "server "default" "directive. And in that I did expected "$SERVER_NAME"
to be the DNS name of the server, not the word "default".
Is there a table of what the build in "types" are. Thee should be a refrence to
that
table in the httpd.conf man page.
