- From: <henry.story@bblfish.net>
- Date: Sun, 3 May 2015 12:30:36 +0200
- To: Linked Data Platform WG <public-ldp-wg@w3.org>
> On 3 May 2015, at 12:04, henry.story@bblfish.net wrote: > > Hi, > > the result of a POST is currently according to the spec § 5.2.3.1 > >> LDP clients should create member resources by submitting a representation as the entity body of the HTTP POST to a known LDPC. If the resource was created successfully, LDP servers must respond with status code 201 (Created) and the Location header set to the new resource’s URL. Clients shall not expect any representation in the response entity body on a 201 (Created) response. > > I was wondering if it would make sense for the client to also send back > all the headers as well, such as > > Access-Control-Allow-Origin: * > Allow: OPTIONS, GET, HEAD, POST, SEARCH, PATCH, PIT > Accept-Patch: application/sparql-update > ETag: "1417390950000|Success(922)" > Last-Modified: Sun, 1 April 2015 23:42:30 GMT > This would allow the client to immediately know what further operations it could do on the newly created resource. It would be good if one could also in the result specify which mime types were allowed on a GET on the created resource. Henryt > > > > Henry > > Social Web Architect > http://bblfish.net/ > Social Web Architect http://bblfish.net/
Received on Sunday, 3 May 2015 10:31:06 UTC