Stream: implementers
Topic: Location header on deletes
Lloyd McKenzie (May 27 2016 at 15:17):
According to the HTTP spec, location header is "N/A" on a delete. However, technically we're creating a new "version". Is there a problem with it being returned optionally? If I send a batch of deletes, it'd be really nice to have the URLs of the things that I'm deleting rather than having to match solely on position. (Alternatively, can I just use the etag?)
Grahame Grieve (May 27 2016 at 22:35):
@Eric Prud'hommeaux what become of the etag on delete question? I don't remember?
James Agnew (Jun 17 2016 at 21:47):
Why is that N/A? This does seem odd...
Grahame Grieve (Jun 17 2016 at 22:10):
http rules, I think
James Agnew (Jun 17 2016 at 22:14):
Ah interesting... I'm fairly sure HAPI isn't conformant on that actually. Damn.
Lloyd McKenzie (Jun 19 2016 at 02:55):
etag turns out to not really help as it just gives the version and what I'd really like is the id - I'm doing a batch of deletes and the only thing that ties the response to the request is its position - which isn't ideal.
Last updated: Apr 12 2022 at 19:14 UTC
