[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: More on REST and HTTP status codes

• To: xml-dev@l...
• Subject: Re: More on REST and HTTP status codes
• From: Miles Sabin <miles@m...>
• Date: Sat, 6 Mar 2004 09:29:45 +0000
• In-reply-to: <404947FB.7060706@c...>
• References: <86znau3eg5.fsf@f...> <DD06300A-6F1B-11D8-95ED-000A95A51C9E@t...> <404947FB.7060706@c...>
• Sender: Miles Sabin <miles@m...>
• User-agent: KMail/1.6

Thomas B. Passin wrote,
> Tim Bray wrote:
> > 404.  The URI is opaque.  There is no such resource.  -Tim
>
> I don't think so. Rfc 2396 says
>
> "The query component is a string of information to be interpreted by
>  the resource."
>
> This shows that the query string is not actually part of the resource
> specification.

The text of section 3.4 has been completely rewritten for RFC 2396bis 
[1]. The new sentence corresponding to the one you quoted reads,

  The query component contains non-hierarchical data that, along with
  data in the path component, serves to identify a resource within the
  scope of the URI's scheme and naming authority (if any).

the implication being that the query component is an intrinsic part of 
resource identification, on a par with the path component, rather than 
being auxilliary information which is fed to an already identified 
resource.

[1] http://gbiv.com/protocols/uri/rev-2002/rfc2396bis.html

Cheers,


Miles

• References:
  • More on REST and HTTP status codes
    • From: ari@c... (K. Ari Krupnikov)
  • Re: More on REST and HTTP status codes
    • From: Tim Bray <tbray@t...>
  • Re: More on REST and HTTP status codes
    • From: "Thomas B. Passin" <tpassin@c...>

• Prev by Date: Re: More on REST and HTTP status codes
• Next by Date: Re: Enumerated Lists
• Previous by thread: Re: More on REST and HTTP status codes
• Next by thread: Re: More on REST and HTTP status codes
• Index(es):
  • Date
  • Thread