FaceOnMars - 1:03 am on Jan 21, 2013 (gmt 0)

Thank you for the clarification on 410. I thought it meant gone, but could come back ... with a higher emphasis (vs. 404) on could come back. Regardless, it's easier to keep all pages I'm referring to as 404.

Yeah, I kind of wondered if it might have been an issue re: where along the assembly line apache might still allow for the custom error page to be called. In any case, thank you g1 for pointing out the PHP method ... which I'm not sure of the Perl equivalent, but it quickly got me to thinking that it would be easy enough to simply open up the actual custom error message file and print it, but not sure if it's the wisest way to go about it - not sure about unintended consequences regarding resource utilization if the page gets hits alot for whatever reason?

if ($CurrentPage > "$RoundedCategoryPageCount") {

print "Status: 404 Not Found\r\n";

print "Content-Type: text/html\r\n\r\n";

open (PAGENOTFOUND, "/absolute/path/to/custom/error/message/file.html") || die "couldn't open the file!";

while ($contents = <PAGENOTFOUND>) {
print $contents;
}

close (PAGENOTFOUND);

exit;

}