On Friday, October 15, 1999 7:34 PM, Leslie Mikesell [SMTP:[EMAIL PROTECTED]] wrote:
What is the most straightforward way to make a RewriteRule
map an arbitrary URL directly to a handler? I can do it
by setting a handler for a directory, putting the file there
and rewriting to that location,
I need to have 2 PerlHandler 's in the httpd.conf file, but when I put
them both in...the html page from that location gets interpreted 2 times.
here is the Location code
Location /embperl2
SetHandler perl-script
PerlHandler Apache::BASEREF
PerlHandler HTML::Embperl
Options ExecCGI
When I told that ASP slower than Embperl - Joshua Chamas said that he know
it, but was surprised by huge difference, he tuned the ASP, I upgraded
Embperl to 1.2b9 and results interchanges.
If you tune Embperl (set EMBPERL_OPTIONS to 8083), the result interchange
again, but you loose some of
According to Eric Cholet:
What is the most straightforward way to make a RewriteRule
map an arbitrary URL directly to a handler?
Do you really need to rewrite, I mean can't you just use
a Location container ?
Yes, that will work, but putting all of the special cases into
RewriteRules
Gerald is too modest. On the simplest of scripts, the Hello
World bench, the fastest Embperl config smokes Apache::ASP's best
by at least 45%, on the same box. Check out:
http://www.chamas.com/hello_world.html
A simple mod_perl handler is in turn is 30+% faster than Embperl.
Your
Aha. I bet sfio is the problem, and I bet your solution is the correct
one. I think that when you use sfio, mod_perl doesn't need to tie
STDOUT (it uses other methods for redirection), so Apache::Filter gets
confused. Can anyone confirm these hypotheses?
If the following patch works for you,
