[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Suggest slight change in description of Slug




A. Pagaltzis wrote:
*grmf* And then I went and accidentally dropped the specific
qualification from the text. What I meant is, of course, this:

    Slug is an HTTP entity-header whose presence in a POST to a
    Collection constitutes a request by the client to use the
    header value as part of the URI normally used to retrieve the
    to-be-created Member Resource.

Regards,

We define Slug as an "entiy-header" that is only present in a POST request, and has no meaning elsewhere. Doesn't that make it a request header? If so, it must be clearly stated as such. ยง5.3 of RFC 2616 clearly states that

   ...[N]ew or experimental header fields MAY be given the semantics of
   request-header fields if all parties in the communication recognize
   them to be request-header fields.