Timeline for When to use HTTP status code 404 in an API
Current License: CC BY-SA 3.0
8 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jul 3, 2013 at 9:38 | comment | added | imel96 | @IlmariKaronen what I mean is, if /GoalTree/Get?versionDate=2000 is a resource, then how can I send a GET request with query to that resource instead of to /GoalTree/Get ? I guess that's one of the differences from Rest. | |
| Jul 3, 2013 at 8:53 | comment | added | Ilmari Karonen |
@imel96: You can request it from the server and get some data back. Or you could do one of the other things HTTP allows you to do with a resource, like try to POST some data to it (which may or may not do anything useful) or even try to replace it entirely with PUT (which, again, may or may not work). But typically, just requesting the resource with GET would be the main use case.
|
|
| Jul 3, 2013 at 7:33 | comment | added | imel96 | @IlmariKaronen you're right. I've confused HTTP with REST. Still doesn't seem right though because I'm not sure what can you do with a resource with URI like /GoalTree/Get?versionDate=2000BC | |
| Jul 3, 2013 at 6:25 | comment | added | Ilmari Karonen | ...and that this combined URI identifies a specific resource which the client may request by sending that URI to the server. In any case, RFC 2616 (HTTP) simply defines a resource as "A network data object or service that can be identified by a URI, as defined in section 3.2." and goes on to say that "As far as HTTP is concerned, Uniform Resource Identifiers are simply formatted strings which identify--via name, location, or any other characteristic--a resource." | |
| Jul 3, 2013 at 6:23 | comment | added | Ilmari Karonen | @imel96: I think you're misinterpreting RFC 1630: the paragraph you quote in your earlier comment reads, in full: "The question mark ("?", ASCII 3F hex) is used to delimit the boundary between the URI of a queryable object, and a set of words used to express a query on that object. When this form is used, the combined URI stands for the object which results from the query being applied to the original object." (emphasis mine). Thus, it's clear that the query string is indeed part of the URI (even though the part before the query string is, necessarily, also a valid URI by itself)... | |
| Jul 3, 2013 at 6:04 | comment | added | imel96 | there's no dilemma. this answer is not based on what resource is defined as in the related rfc. see my comment under @LegoStormtroopr answer. | |
| Jul 3, 2013 at 5:49 | comment | added | Marcel | The dilemma well explained. | |
| Jul 3, 2013 at 5:29 | history | answered | Ilmari Karonen | CC BY-SA 3.0 |