Re: internal_redirect to randomly named filename

2004-02-10 Thread Geoffrey Young
[EMAIL PROTECTED] wrote: > On Tue, Feb 03, 2004 at 11:09:31AM -0500, Geoffrey Young wrote: > >>I don't see why you need to use either with internal_redirect() - just pass >>it the URI and let Apache handle it. you would use a subrequest (initiated >>from eather of the lookup functions) along wi

Re: internal_redirect to randomly named filename

2004-02-10 Thread [EMAIL PROTECTED]
On Tue, Feb 03, 2004 at 11:09:31AM -0500, Geoffrey Young wrote: > I don't see why you need to use either with internal_redirect() - just pass > it the URI and let Apache handle it. you would use a subrequest (initiated > from eather of the lookup functions) along with $sub->run() if you wanted to

Re: internal_redirect to randomly named filename

2004-02-03 Thread Geoffrey Young
[EMAIL PROTECTED] wrote: > Hi All, > Since lookup_uri() is only to be used when the actual > URI physically exists. Having said that how does not tell > it to pretend that a randomly generated virtual file exists? > Is that what lookup_filename() is for? lookup_uri() will issue a subrequest

internal_redirect to randomly named filename

2004-02-02 Thread [EMAIL PROTECTED]
Hi All, Since lookup_uri() is only to be used when the actual URI physically exists. Having said that how does not tell it to pretend that a randomly generated virtual file exists? Is that what lookup_filename() is for? I am wanting to do a internal_redirect() to a virtual file whose name is al