RE: How to identify existing resource in a POST(a) request
"Markus Lanthaler" <[email protected]>
| Newsgroups | gmane.comp.web.services.rest |
|---|---|
| Message-ID | <[email protected]> |
On Saturday, October 27, 2012 2:53 PM, Paul Moore wrote. > My question is really regarding whether use of the 'Referer' > header is a sensible way to identify the URI of the > representation that initiated the request. So you are saying that every representation of a person has to contain a link to your "friend service"? So, to take your example, graph.facebook.com/2 must somewhere contain a link to example.com/friends? Otherwise, how did that URI "initiate the request"? I think HTTP (bis) is quite clear on this: The "Referer" [sic] header field allows the client to specify the URI of the resource from which the target URI was obtained (the "referrer", although the header field is misspelled.). So I would say it's a bad design decision to use the referer header for the scenario you are outlining. Best, Markus -- Markus Lanthaler @markuslanthaler