- From: Richard Light <richard@light.demon.co.uk>
- Date: Thu, 9 Jul 2009 12:13:54 +0100
- To: Peter Krantz <peter.krantz@gmail.com>
- Cc: public-lod@w3.org, semantic-web@w3c.org
In message <7b9ad66d0907090406t37f29aa0qc7271d094914a81@mail.gmail.com>, Peter Krantz <peter.krantz@gmail.com> writes >> >> Attached is an IIS Active Server Page which handles 404 "page not found" >> errors. The logic is that since the abstract URLs/PSIs representing a >> concept/subject do not have a corresponding page, they will end up here. > >This sounds interesting. Is it possible to prevent IIS to send the 404 >status code before continuing processing? Yes, that's the whole idea. By the time the 404 handler has finished its work, the client will receive either a 303 response (for a redirect), a 200 response (when it actually delivers content), or a 404 (if it can't handle the URL request at all). Richard -- Richard Light
Received on Thursday, 9 July 2009 11:15:32 UTC