On Mon, 26 May 2008, Kurt Hansen wrote:
>> ServerName il2.netteq.com
>> DocumentRoot /var/web/netteq.com/il2/portal
>>
>> PerlRequire /var/web/netteq.com/il2/startup.pl
>> PerlTaintCheck On
>> PerlWarn On
>>
>> # Mason
>> PerlSetVar MasonCompRoot /var/web/netteq.com/il2/portal
>> PerlSetVar MasonDataDir /var/web/netteq.com/il2/mason-data
>>
>> <LocationMatch "(\.html|\.txt|\.pl)$">
>> SetHandler perl-script
>> PerlHandler HTML::Mason::ApacheHandler
>> #PerlHandler MyMason::MyApp
>> </LocationMatch>
>>
>> <LocationMatch "(\.m(html|txt|pl)|dhandler|autohandler)$">
>> SetHandler perl-script
>> PerlInitHandler Apache::Constants::NOT_FOUND
>> #PerlHandler MyMason::MyApp
>> </LocationMatch>
>
> Are you by chance telling mod_perl and Apache to ignore autohanders and
> dhandlers. What happens if you take out the autohandler in the second
> LocationMatch? How about the dhandler?
Actually, you _want_ mod_perl to ignore autohandlers and dhandlers, which
is exactly what the above config does. The {d,auto}handler dispatching is
done inside Mason. All you need to do is tell mod_perl to let Mason handle
certain requests. Then Mason looks for autohandlers internally.
> Another possibility - is there a space before the % $m->call_next() in
> your autohandler? %-lines must start on the first character; a space
> will cause Mason to skip it and display it, as you have seen. I got
> caught by that a lot when I was starting out.
That could definitely do it. Of course, then you should see that line in
the output.
-dave
/*==========================
VegGuide.Org
Your guide to all that's veg
==========================*/
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2008.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Mason-users mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mason-users
