Alvaro Lopez Ortega wrote:
> Handlers are only content generator for the web. All of them are
> equipotent, basically because there is not a way to set a precedence
> order, and because it wouldn't make much sense anyway.
I must not understand the intended behavior, so I'll express the way I
had hoped to eventually write my config file, and then try to sit still
and let the competent people take over. *wink*
My config file currently uses a Directory for each prefixed redir I'd
like to perform. So right now I have this:
Directory / { Handler common }
Directory /trackback { Handler redir { .. } }
Directory /archives { Handler redir { .. } }
Directory /feeds { Handler redir { .. } }
I had hoped to eventually drop that because /trackback, /archives, and
/feeds don't exist - using a Directory didn't make sense to me. However,
when I attempted to consolidate those lines in the following manner, it
didn't work for me:
Directory / {
Handler redir {
Rewrite "/trackback/(.+)\.php" ..
Rewrite "/archives/(.+)\.html" ..
Rewrite "/feeds/(.+)\.xml" ..
}
Handler common
}
If that's not how things are intended to work, that's fine. I had just
assumed I could have a fallback Handler, which is why I had thought
establishing a precedence based on the order of appearance would be useful.
> I propose to use the same precedence as the definition of the
> entries in the configuration file: first entries have more priority.
I like it.
Thanks!
Kurt McKee
_______________________________________________
Cherokee mailing list
[email protected]
http://www.alobbs.com/cgi-bin/mailman/listinfo/cherokee
