At the moment, CGI processes are mandated to take full responsibility of the path they've been given. This is true whether or not the path exists - asking the server for /nosuch.asp requires MacASP to generate its own error page.
What I'd like to see is deferral return support - the CGI script will return a special line like:
Decline: 404
When MacHTTP detects this, it will start another iteration of action handling, this time with the deferral code as the response type. If the code was 404, it will run the error directive; if the code was 403, it would run the no-access directive.
There are two situations on my server at present using this set-up. One is uniform error pages - I'd like MacASP to make use of my standard error pages. This is trivial, though, as I can set system.asp to contain the error page in question. The more fun one is that I perform redirections using error acgi, and where redirections involve .asp pages, MacASP will simply deny knowledge of the page and return an error. I've set up a complex system involving special system.asp code and a MacASP plugin that forwards the error over to error acgi, and then the error page is passed back to MacHTTP via the plugin and then system.asp. This system does work flawlessly, but it would need coding from scratch for MacPerl or Biferno, or any other CGI that wants to return an error page of any kind.
Hence the need for CGIs to be able to decline processing a given path.