W3C home > Mailing lists > Public > public-lod@w3.org > July 2009

Re: 303 redirection strategy for IIS

From: Juan Sequeda <juanfederico@gmail.com>
Date: Thu, 9 Jul 2009 14:04:17 +0200
Message-ID: <f914914c0907090504g4b460511kdc89e99df5f138b@mail.gmail.com>
To: Richard Light <richard@light.demon.co.uk>
Cc: Peter Krantz <peter.krantz@gmail.com>, public-lod@w3.org, semantic-web@w3c.org
Hi Richard

This is a great addition to the ConNeg 303 section on linkeddata.org.

However, would you be able to host the source code and then I can just link
to it from linkeddata.org?


Juan Sequeda, Ph.D Student
Dept. of Computer Sciences
The University of Texas at Austin

On Thu, Jul 9, 2009 at 1:13 PM, Richard Light <richard@light.demon.co.uk>wrote:

> 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 12:04:52 UTC

This archive was generated by hypermail 2.4.0 : Thursday, 24 March 2022 20:29:44 UTC