Forum OpenACS Q&A: Re: Do *.vuh files other than index.vuh make any sense?

3: Re: Do *.vuh files other than index.vuh make any sense? (response to 2)

Posted by Tilmann Singer on 11/13/02 12:32 AM

I agree that the latter would be nicer.

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.

4: Re: Do *.vuh files other than index.vuh make any sense? (response to 3)

Posted by Tilmann Singer on 11/13/02 01:09 AM

Here's a patch: https://openacs.org/bugtracker/openacs/patch?patch%5fnumber=5

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?