Pierre M. wrote:
I've suggested yourownscript.php?param=something
Ah I misread that, but i did answer it in my previous post.
My own phpscripts do not forward to 404 when an unknown parameter is given.
I also haven't set up any URL rewriting (yet).
Though I do think I found the problem. In content.functions.php I see this:
function content_get_template($tpl_name, &$tpl_source, &$smarty_obj)
{
global $gCms;
$config =& $gCms->GetConfig();
$pageinfo = &$gCms->variables['pageinfo'];
if (isset($pageinfo) && $pageinfo->content_id == -1)
{
#We've a custom error message... return it here
[glow=yellow,2,300]header("HTTP/1.0 404 Not Found");[/glow]
[glow=yellow,2,300]header("Status: 404 Not Found");[/glow]
if ($tpl_name == 'content_en')
$tpl_source = get_site_preference('custom404');
else
$tpl_source = '';
return true;
}
else.....
I believe that when sending those headers (while using IIS) everything else is ignored. So that would explain why I can't get the custom 404 message, but can get the site-down message.
I will investigate if any settings in IIS can prevent this and I will post my findings here in case more people have this probem or to enable you to make the custom 404 compatible with IIS.
)