- From: Julian Reschke <julian.reschke@gmx.de>
- Date: Tue, 29 Jul 2008 20:02:35 +0200
- To: Mark Baker <distobj@acm.org>
- CC: Mark Nottingham <mnot@mnot.net>, HTTP Working Group <ietf-http-wg@w3.org>
Mark Baker wrote: > On 7/29/08, Julian Reschke <julian.reschke@gmx.de> wrote: >> Mark Baker wrote: >> >>> On 7/29/08, Julian Reschke <julian.reschke@gmx.de> wrote: >>> >>>> Proposal: just drop "PUT and POST" from the sentence, making it: >>>> >>>> "The meaning of the Content-Location header in requests is >>>> undefined; servers are free to ignore it in those cases." >>>> >>> Eek, no, that seems to head in the opposite direction, as its meaning >>> is perfectly clear AFAICT. I say we just remove the whole sentence. >>> >> I see. >> >> How about saying just: >> >> "The meaning of the Content-Location header in requests is undefined." >> >> Because otherwise we'll get people asking where it's defined :-) > > 8-) But it's an entity header, so it means the same thing in requests > and responses. So, for instance for PUT, servers are expected to store it and return them in a subsequent GET? BR, Julian
Received on Tuesday, 29 July 2008 18:03:18 UTC