CrossClj

1.1.44 docs

SourceDocs



RECENT
    VARS
    available?
    capture-cookies
    capture-proxy-headers
    check-modification-time
    compute-etag
    create-response
    get-new-properties
    get-properties
    if-match
    if-none-match
    invoke-method
    known-method?
    logging
    method-allowed?
    parse-parameters
    process-request-body
    return
    safe-read-content-length
    select-representation
    TRACE
    uri-too-long?

    « Index of all namespaces of this project

    (available? ctx)
    Is the service available?
    
    (capture-cookies ctx)
    (capture-proxy-headers ctx)
    (check-modification-time ctx)
    (compute-etag ctx)
    (create-response ctx)
    (get-new-properties ctx)
    If the method is unsafe, call properties again. This will
    pick up any changes that are used in subsequent interceptors, such as
    the new version of the resource.
    (get-properties ctx)
    (if-match ctx)
    (if-none-match ctx)
    (invoke-method ctx)
    Methods
    
    (known-method? ctx)
    (logging ctx)
    (method-allowed? ctx)
    Is method allowed on this resource?
    
    (parse-parameters ctx)
    Parse request and coerce parameters. Capture cookies.
    
    (process-request-body {:keys [request], :as ctx})
    Process the request body, if necessary. RFC 7230 section 3.3 states
    "The presence of a message body in a request is signaled by a
    Content-Length or Transfer-Encoding header field. Request message
    framing is independent of method semantics, even if the method does
    not define any use for a message body".
    
    Therefore we process the request body if the request contains a
    Content-Length or Transfer-Encoding header, regardless of the method
    semantics.
    (return ctx)
    (safe-read-content-length req)
    (select-representation ctx)
    Proactively negotatiate the best representation for the payload
    body of the response. This does not mean that the
    response will have a payload body (that is determined by the
    method (which we know) and the status code (which is yet to be
    determined).
    (uri-too-long? ctx)