Skip to content

Latest commit

 

History

History
54 lines (44 loc) · 2.54 KB

README_response.md

File metadata and controls

54 lines (44 loc) · 2.54 KB
  1. System (white)
  2. Request (blue)
  3. Accept (green)
  4. Retrieve (white)
  5. Precondition (yellow)
  6. Create/Process
  7. Response (cyan)
  8. Alternative (gray)

HTTP headers status

Response

callback output default
N3 is_create_done :bin T / F is_process_done :bin
N6 create_see_other :bin T / F see_other :bin
content_types_provided:handler :bin T / F
to_content : in T / F FALSE
- to_resource_content :bin T / F
- content_location :var URI
- vary :var [ [ HeaderName ] ]
- expires :var Date
- last_modified :var Date Now
- etag :var ETag
N14 is_process_done :bin T / F TRUE
N10 see_other :bin T / F FALSE
path :var URI
N9 has_multiple_choices :bin T / F FALSE
N8 content_types_provided:handler :bin T / F
to_content : in T / F FALSE
- to_resource_content :bin T / F
- content_location :var URI
- cache :var String
- vary :var [ [ HeaderName ] ]
- expires :var Date
- last_modified :var Date Now
- etag :var ETag

FIXME Explanations needed

to_resource_content :bin

Return TRUE if the content is resource content, as in this content would be the response to a GET/HEAD request to the resource identified by the Content-Location header.

By default, this returns TRUE if a Content_Location header has been set (e.g. during the create or process callback).

content_location :var

Return a Content-Location header.

By default, this returns an already set Content-Location response header or the location of the request target i.e. the resource would reply with its own content.