response
Click on the red underlined text to get to the source
... This document specifies a Hyper Text Coffee Pot Control Protocol
(HTCPCP), which permits the full request and responses necessary to
control all devices capable of making the popular caffeinated hot
...
... the produced data which shall be returned as the entity in the
response and not the source text of the process, unless that text
happens to be the output of the process.
...
... The "safe" response header field. ...
...
[SAFE] defines a HTTP response header field, "Safe", which can be
used to indicate that repeating a HTTP request ...
... HTTP, the "Accept" request-header field is used to specify media
types which are acceptable for the response. However, in HTCPCP, the
response may result in additional actions on the part of the
...
... media
types which are acceptable for the response. However, in HTCPCP, the
response may result in additional actions on the part of the
automated pot. For this reason, HTCPCP adds a new header field,
...
... This return code is normally interpreted as "The resource identified
by the request is only capable of generating response entities which
have content characteristics not acceptable according to the accept
headers ...
... have content characteristics not acceptable according to the accept
headers sent in the request. In HTCPCP, this response code MAY be
returned if the operator of the coffee pot cannot comply with the
Accept-Addition request. Unless the request was a HEAD request ...
... Accept-Addition request. Unless the request was a HEAD request, the
response SHOULD include an entity containing a list of available
coffee additions.
...
... K. Holtman. "The Safe Response Header Field", September 1997. ...