Dossy wrote:
On 2003.02.17, Ross Simpson <[EMAIL PROTECTED]> wrote:
The problem with ns_register_proc is that it expects the requested file
to exist -- something I don't want. I want a proc run for any request
matching a pattern, and after that proc runs, for the connection to be
closed.
That's strange -- I use ns_register_proc for URLs where the document the
URL refers to /definitely/ do not exist in the pageroot. Weird.
Filters work the same as procs in that respect, since they are based on
the url, not what exists under pageroot. However, only one proc can be
registered for any url, so when that proc fires, the request is
considered served, and the process moves on to run any trace filters.
The fastpath proc is registered on /* for methods GET, POST, HEAD, so if
you don't register anything more specific, the fastpath proc will pick
up the request processing. The steps involved in a request are:
1. run all preauth filters that match the url pattern in the order they
were registered during startup, or until any filter returns
filter_break or filter_return
2. auth request unless filter_return returned above,
3. same as 1 for postauth filters unless a preauth filter returned
filter_return
4. run closest matching registered proc, assuming filter_return was not
returned
5. run any trace filters unless one returns filter_return or filter_break
--Tom Jackson
