I think some these statements aren't right: > the response to a POST is supposed to be a Location header of the created record The HTTP spec says otherwise:

I think some these statements aren't right: > the response to a POST is supposed to be a Location header of the created record The HTTP spec says otherwise: The action performed by the POST method might not result in a resource that can be identified by a URI. In this case, either 200 (OK) or 204 (No Content) is the appropriate response status, depending on whether or not the response includes an entity that describes the result. > You cannot return multiple Locations in a header, for example, when multiple records are created. Again the HTTP spec allows you to manage this (though not in the header): 10.2.2 201 Created The request has been fulfilled and resulted in a new resource being created. The newly created resource can be referenced by the URI(s) returned in the entity of the response, with the most specific URI for the resource given by a Location header field. The response SHOULD include an entity containing a list of resource characteristics and location(s) from which the user or user agent can choose the one most appropriate. Source: http://tools.ietf.org/html/rfc2616 http://tools.ietf.org/html/rfc2616 edit: was quoting HTTP 1.0 rather than 1.1