Geek Answers Handbook

Including the created resource in the HTTP POST response?

RFC7231 says that the server should respond to a POST request that creates the resource, with status 201 and a location header for the new resource. In some situations, it may be convenient for the server to include a representation of the created resource in its response, but in other cases it will be a waste of bandwidth.

Could this be a good place to reconcile content as part of an email request? If so, what request headers should be sent to indicate that the client would like to return the resource in addition to the Location header?

+4
source share
1 answer

I would suggest using the Preference header:

Inquiry:

PUT /xxx
Prefer: return=representation

Answer:

201 Created

{ ... created resource representation ... }

. http://tools.ietf.org/html/rfc7240

+3

More articles:


All Articles