[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: ari@c... (K. Ari Krupnikov)
• Date: 06 Mar 2004 22:50:35 -0800
• In-reply-to: <DD06300A-6F1B-11D8-95ED-000A95A51C9E@t...>
• References: <86znau3eg5.fsf@f...><DD06300A-6F1B-11D8-95ED-000A95A51C9E@t...>
• Sender: ari@f...
• User-agent: Gnus/5.09 (Gnus v5.9.0) Emacs/21.3

Tim Bray <tbray@t...> writes:

> On Mar 5, 2004, at 6:19 PM, K. Ari Krupnikov wrote:
> 
> > What status should a server return for a request such as
> >
> > http://example.com/catalog?product=0001
> >
> > if the resource that identifies the catalog (example.com/catalog) is
> > available but cannot find the product identified in the query string?
> >
> > The question boils down to whether an HTTP URI is opaque or if the
> > question mark has predefined semantics. (The specs would have me
> > believe the former, but the practice seems to be the latter).
> 
> 404.  The URI is opaque.  There is no such resource.

Tim,

Do you have a reference to any sites that actually exhibit this
behavior?

Ari.

-- 
Elections only count as free and trials as fair if you can lose money
betting on the outcome.

• Follow-Ups:
  • Re: More on REST and HTTP status codes
    • From: Seairth Jacobs <seairth@s...>

• 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...>

• Prev by Date: Re: More on REST and HTTP status codes
• Next by Date: RE: W3C suckered by Microsoft?
• 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