Hi Tim,
On Thu, Jul 22, 2010 at 03:36, Tim Watts <t...@dionic.net> wrote:
> I want .html files to be served as complete content, and .page files to
> be wrapped with the HTML head stuff, a menu and a footer. The idea is
> that most of my content will be .page files, wrapped with a constant
> set of stuff. But I can stick a .html file in and know that it will not
> be wrapped, should I need to...
Presuming I'm understanding what you're doing *and* you have sysadmin
access to edit the web server's configuration files, another option is
to let the web server do this for you. That is, if the file ends with
.html, display it; if it ends with .page, send it to the handler.
As I'm not doing exactly what you're doing, I'm not sure if this will
work...but my Apache2 httpd.conf looks something like this:
<Directory /var/www/>
<FilesMatch "(\.html)$">
SetHandler perl-script
PerlResponseHandler Handler
</FilesMatch>
<FilesMatch "(\.mhtml|dhandler|autohandler|syshandler)$">
SetHandler perl-script
PerlResponseHandler Apache2::Const::NOT_FOUND
</FilesMatch>
</Directory>
So, what I've done is to make mason handle .html files, but things I
don't want viewed by the user, I send a NOT_FOUND. This seems similar
to what you are doing -- I presume if you remove the second part and
change \.html to \.page, .html files will be displayed as-is without
going through the handler...
Of course, if you don't have root access, then you're out of luck...
Ray
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mason-users mailing list
Mason-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mason-users
