Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

Well, if the server understands the payload, it can return it in a different representation. There is nothing wrong with that. But a GET should always return the original payload when requested with the Accept header that matches the original Content-Type of the PUT request.

edit:

Better is to use a PUT for different representations:

  PUT /foo
  Content-Type: application/json
  
  {"foo":""}

  PUT /foo
  Content-Type: text/xml
  
  <foo></foo>


Seems to be no reason why GET should return the original payload. No client should even expect that as the resource could easily have been changed by another client in between requests.


Obvious, but thats not the point.


What is the point? GET isn't even guaranteed to return the same payload every time, without PUT. Look at this website for example. The idea that you need to PUT something that be GET in exactly the same representation makes no sense given these basic facts.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: