>> You were close. It's default-handler.
>>
>> http://httpd.apache.org/docs/handler.html
>And in mod_perl docs:
>http://perl.apache.org/docs/1.0/guide/config.html#Overriding_E_lt_LocationE
_gt__Se>tting_in__Sub_Location_
__
Thanks, that was what I was looking for.
Thomas Whitney
Rick Myers wrote:
> On Aug 12, 2002 at 11:50:56 -0600, Thomas Whitney wrote:
>
>> I was following this thread with interest because I want to do something
>>like this. I started searching on list archive for the above mentioned
>>syntax, I searched for 'static content', then 'default handl
On Aug 12, 2002 at 11:50:56 -0600, Thomas Whitney wrote:
> I was following this thread with interest because I want to do something
> like this. I started searching on list archive for the above mentioned
> syntax, I searched for 'static content', then 'default handler', but with
> no luck
>> If I do set my script to answer all requests, how do I tell the
>> webserver to show the static content that exists under the requested
>> url?
>You have to make the default handler pick it up. I forget the exact
>syntax, but there were some examples posted to the mailing list a while
>back.
Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: Friday, August 09, 2002 8:01 AM
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]
Subject: Re: Handler Concept / Question
> Does anyone have any points of view on whether the script should just
> be a 404 handler or whether
> Does anyone have any points of view on whether the script should just
> be a 404 handler or whether I should set a handler to listen to all
> requests and have my script determine what to do, or another way to do
> it?
Those are both fine. The 404 handler approach will give slightly better
per
The basic concept I want
to accomplish is to allow for static and dynamic content to be accessed
from any url and be transparent to the
visitor.
i.e
publish a static page
called /foo/bar.htm
have a dynamic page
called /foo/foobar.htm
I imagine there are a
couple of different ways to d