]
Subject: Re: SSI and mod_perl
At 23:09 27.08.2002, Jay Thorne wrote:
In a mod_perl handler, in the m_p1.x/apache1.3 api, Is there a quick way to
tell apache
I'm done, here's my content, and I want you to run this through
mod_include
before you send it to the user
You might want to try a filter
At 23:09 27.08.2002, Jay Thorne wrote:
In a mod_perl handler, in the m_p1.x/apache1.3 api, Is there a quick way to
tell apache
I'm done, here's my content, and I want you to run this through mod_include
before you send it to the user
You might want to try a filter, for example
On August 27, 2002 02:16 pm, Per Einar Ellefsen wrote:
At 23:09 27.08.2002, Jay Thorne wrote:
In a mod_perl handler, in the m_p1.x/apache1.3 api, Is there a quick way
to tell apache
I'm done, here's my content, and I want you to run this through
mod_include before you send it to the user
On Tue, 27 Aug 2002, Jay Thorne wrote:
On August 27, 2002 02:16 pm, Per Einar Ellefsen wrote:
At 23:09 27.08.2002, Jay Thorne wrote:
In a mod_perl handler, in the m_p1.x/apache1.3 api, Is there a quick way
to tell apache
I'm done, here's my content, and I want you to run this through
On August 27, 2002 03:32 pm, Randy Kobes wrote:
Thats close to what I want to do, but as the existing code has its entry
already in the webserver config.
What I mean is something like $r-next(mod_include); OK;
or items to that effect.
Is there a direct apache api hook I can use to
