Forum OpenACS Q&A: Do *.vuh files other than index.vuh make any sense?
The documentation at http://openacs.org/doc/openacs-4/rp-design.html does not even mention index.vuh. I wonder if I am missing something here - are the docs just wrong and need an update or what would be the purpose of a non-index .vuh?
There are also zero non-index.vuh's in the toolkit.
I think the latter is more consistent and allows for all to choose their preferred style of URL and file organization.
I think it can be tracked down to the proc rp_path_prefixes (only used in rp_filter) which returns
/foo/bar/ /foo/ /when given the path /foo/bar/. Changing it to return
/foo/bar/ /foo/bar /foo/ /foo /seems to do the trick. This needs some further testing though if path_info is always correct etc.
Note that for index.vuh's the value of [ad_conn path_info] is always without a slash at the beginning. For a foo.vuh file it can either be an empty string (request for /foo directly), a single slash (request for /foo/) or more, with a beginning slash, e.g. /bar/baz for the request /foo/bar/baz.
This might be unexpected because it's different from index.vuh's, but I think it is the right behaviour because otherwise it would not be possible to distinguish if /foo or /foo/ was requested.
Anybody who has the time for some more testing?