Reputation: 18983
Specification's talking about requests for "the same resource". But I failed to find any explanations as to what it exactly is. Is it the URL? Or probably requests with the same URL and different headers are considered as different resources? I'm using custom headers as a way to influence what's returned by the server. And seem to experience some issues because of that.
Upvotes: 0
Views: 29
Reputation: 818
A URL identifies a resource, and a resource is just some chunk of information. This article succinctly describes the two's relation:
EX:
If I were to make an Http GET request as such - GET path/to/res/file - I would either get a 200 response with the file resource in the message body, or if something went wrong, I might get something like a 404 or a 500, depending on the server implementation.
http://www.jmarshall.com/easy/http/#resources
http://en.wikipedia.org/wiki/Uniform_resource_locator
http://en.wikipedia.org/wiki/Web_resource
I hope that clears it up a little for you.
Upvotes: 1