Well, customising the "file not found" response (via
/global/file-not-found.html) does work
in the specific case of HTML files. This is not because of an
AOLserver level configuration but because processing of all html
files goes through tlc/ad-html.tcl and that specifically checks for
file existance and returns the (customised) response if not.
That actually covers my main requirement; but I do still wonder:
- Is there a way of customising the other exception responses?
- Is there even a way of customising the file-not-found response to
work for all file types?
- Even in the existing handling of html files not found, might
it be preferable to use a http redirect? (The potential advantage
would be to allow these exception responses to be authored as adp
rather than necessarily static html.)
Cheers,
- Barry.
