httpd-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Mark H. Wood" <mw...@IUPUI.Edu>
Subject Re: [users@httpd] Figuring out the order in which directives apply
Date Tue, 29 Jan 2008 14:51:09 GMT
Thank you for your very helpful response.

On Mon, Jan 28, 2008 at 10:54:47PM +0000, Nick Kew wrote:
> On Mon, 28 Jan 2008 16:54:32 -0500
> "Mark H. Wood" <mwood@IUPUI.Edu> wrote:
> > Is there some document I can read to help me understand the order in
> > which configuration directives from different modules apply?
> maybe you're looking for

Maybe not.  That one does a good job of settling how HTTPD decides
which directives apply, but I don't get much of a sense of order
w.r.t. modules.
> > In this instance I wanted to know whether I could use Allow/Deny rules
> > before a request gets picked off and handed over to a servlet
> > container by mod_jk.  There didn't seem to be any obvious way to
> > answer the question except by experiment.  (My result:  I *think* this
> > works.)
> That's simple: allow/deny rules apply before any content handler.
> To do otherwise would be nonsensical.

One would think so, but I try not to assume.  I've had strange things
happen when working with mod_jk, and am still learning to make it do
what I want.
> This might be clearer in some of the developer docs, such as

Better, but still not clear as to just when e.g. mod_jk steps in and
says, "this request is mine; I'll let you know what the response
should be".


This one helps a lot.  In this instance, the phrase "content
generation" is what I needed to see.  Still assuming, but with better
reason: access control seems more like a metadata function, while
grabbing the request and giving it to a different program to turn into
the response sure ought to be content generation.

The two-axis processing diagram also told me a lot.  Maybe not much
bearing on this particular problem, but I feel that I understand
things better generally and have bookmarked it for further study.

Mark H. Wood, Lead System Programmer   mwood@IUPUI.Edu
Typically when a software vendor says that a product is "intuitive" he
means the exact opposite.

View raw message