W3C home > Mailing lists > Public > ietf-http-wg@w3.org > January to March 2014

Re: New Version Notification for draft-hunt-http-rest-redirect-00.txt

From: Mark Baker <distobj@acm.org>
Date: Thu, 16 Jan 2014 14:13:38 -0500
Message-ID: <CALcoZio-XM7fhQcBEEhTNjVLCZY7Pdkc1fpa_T14gr7Ko+LfFQ@mail.gmail.com>
To: Phil Hunt <phil.hunt@oracle.com>
Cc: Julian Reschke <julian.reschke@gmx.de>, "scim@ietf.org WG" <scim@ietf.org>, "ietf-http-wg@w3.org Group" <ietf-http-wg@w3.org>, Barry Leiba <barryleiba@computer.org>
On Thu, Jan 16, 2014 at 10:42 AM, Phil Hunt <phil.hunt@oracle.com> wrote:
> Assuming you are refering to the 308 redirect draft. What is the current reference for 308?
>
> REST services need redirects that do not convert to GET. That would corrupt the operation.

None of the redirection codes "convert to GET". What, for example, a
303 response means is that the server is attempting to provide
additional information to the client via another resource. A REST
service would understand this and so know not to try to send another
message with the same meaning as the initial one. It may or may not
choose to send a GET request to that new URI, and if not, would
probably signal this as an error condition.

Mark.
Received on Thursday, 16 January 2014 19:14:06 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 17:14:23 UTC