- From: Booth, David (HP Software - Boston) <dbooth@hp.com>
- Date: Tue, 24 Jan 2006 11:30:28 -0500
- To: "Pat Hayes" <phayes@ihmc.us>
- Cc: <public-swbp-wg@w3.org>
> >Thing-described-by.org provides one easy mechanism for avoiding this > >kind of URI clash. For example, if you have a URI for a Web page > >describing Mark Birbeck: > > http://shutr.net/user/markb > >by prepending "http://thing-described-by.org?" to the URI, you can > >easily create a URI that you can use as an identifier for Mark Birbeck, > >the person: > > http://thing-described-by.org?http://shutr.net/user/markb > >Dereferencing this latter URI will result in a 303-redirect to the > >original Web page that describes him. > > Well, in this particular case it actually yields a 403 Forbidden > error rather than a Web page, but I get the idea. And in any case it > might even be true of Mark Birkbeck that I don't have permission to > access him. Come to think of it, that is more likely than not. Yeah, thing-described-by.org is doing the 303 redirect just fine, but http://shutr.net/user/markb is then giving a 403. :( Here's an example of a URI for me that works fully (gives 200 result): http://thing-described-by.org?http://dbooth.org/2005/dbooth/ > > Simple! No servers to configure, nothing to do. > > > >And if thing-described-by.org is too long for your taste, > you can use > >t-d-b.org instead, such as: > > http://t-d-b.org?http://shutr.net/user/markb > > > >For more information, see http://thing-described-by.org . > > > >Of course, this is not the only way this problem can be > >solved, but I thought it would be relevant to mention it. > > My dear fellow, you are a genius. The whole idea of having to > generate 303 indirects is utterly insane, but given that we have to > do insane things from time to time, at least you have given us a way > to do it relatively painlessly. My heartiest congratulations (and > thanks). Thanks! :) David Booth
Received on Tuesday, 24 January 2006 16:31:21 UTC