> I'm trying to determine a proper way to indicate a requested piece of > information was not found, where the information is keyed not just on the URI > components identifying the HTTP resource, but upon the query string as well.
> If I have a content display resource at, say, http://example.com/path/display, and > that resource generates a > different page depending upon query string*, I might have URLs like: > http://example.com/path/display?page1 > http://example.com/path/display?page2 As you mention in your email, I think the preferred solution would be to translate the URIs in URIs without query strings - one of the reasons being for instance caching information, that HTTP clients are allowed to ignore in case the URI has a query part. Lacking this, I think it's perfectly OK to send a 404 in these cases, since the resource is identified by the whole URI, including the query part; that is, replying 404 on http://example.com/display?pageFoo doesn't imply that http://example.com/display doesn't exist. Hope this helps, Dom -- Dominique Hazaël-Massieux - http://www.w3.org/People/Dom/ W3C/ERCIM mailto:[EMAIL PROTECTED]
signature.asc
Description: Ceci est une partie de message =?ISO-8859-1?Q?num=E9riquement?= =?ISO-8859-1?Q?_sign=E9e=2E?=
