I think there may be a bug or two in the code which handles the case where a non-existent file is requested by a browser, e.g. http://www.mysite.com/xxxx.html, when EmbperlObject is being used. I have EMBPERL_OBJECT_BASE set to base.html, which in turn does Execute (*). The documentation says that if the specified file is not found and EMBPERL_OBJECT_FALLBACK is not defined, then a 404 is returned as normal. However I just get an "internal server error" message, not a 404. I set ErrorDocument 404 in httpd.conf, which would normally catch any 404 (and actually does, if a filetype other than that handled by Embperl is requested), but this situation appears to mean that a 404 is never generated, so the httpd setting never kicks in. I can set EMBPERL_OBJECT_FALLBACK and catch the error, but this appears to have its own problem: If I set EMBPERL_OBJECT_FALLBACK to be subdir/notfound.html, then notfound.html should (I think) be executed like other files which are normally included by base.html. However, this doesn't appear to happen. For example, base.html does Execute('init.html'). I redefine init.html in most subdirectories. However when a non-existent document is requested and EMBPERL_OBJECT_FALLBACK kicks in, and we are redirected to subdir/notfound.html, then subdir/init.html is not executed. Does this make any sense? If it's not clear then I can supply a more rigorous example. TIA -Neil --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
