Hey Eric, thanks for the response. What I'm wondering is if there is a way (perhaps via an appropriate Apache configuration) to avoid the issue of directory requests getting to Mason altogether. What I'm particularly confused about is why the behavior is different for a directory that exists in the file system vs. one that doesn't. Apache already routes /foo/ to /foo/index.html, it does not issue a directory request to Mason. If I can induce the same behavior for / foo/1234/ (i.e. Apache routes that to /foo/1234/index.html) the dhandler's logic remains pleasantly simple. It's possible I'm overestimating the complexity of handling this via a dhandler, but the samples I've found are all substantially more complex than I need--if anyone can point me to a minimal implementation of a dhandler that deals with directory requests I'd appreciate it.
--Ken On Jun 19, 2006, at 4:32 AM, Eric Windisch wrote: > Ken Woodruff wrote: >> Unfortunately the second level URLs ending in a slash do not work >> (presumably Mason declines the request and the dhandler never >> gets invoked). > Exactly... > > http://masonhq.com/docs/manual/Admin.html#allowing_directory_requests > > "If you would like Mason to handle directory requests, set > decline_dirs <http://masonhq.com/docs/manual/ > Params.html#decline_dirs> to 0. The dhandler that catches a > directory request is responsible for setting a reasonable content > type via |$r->content_type()" > | > > |-- > Eric Windisch > | > _______________________________________________ Mason-users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mason-users
