Module Morph.Method
type standard=[|`GETRFC7231§4.3.1. Safe, Cacheable.
|`HEADRFC7231§4.3.2. Safe, Cacheable.
|`POSTRFC7231§4.3.3. Cacheable.
|`PUTRFC7231§4.3.4. Idempotent.
|`DELETERFC7231§4.3.5. Idempotent.
|`CONNECT|`OPTIONSRFC7231§4.3.7. Safe.
|`TRACERFC7231§4.3.8. Safe.
];type t=[|standard|`Other(string)Methods defined outside of RFC7231, or custom methods.
];
let is_safe: standard => bool;Request methods are considered "safe" if their defined semantics are essentially read-only; i.e., the client does not request, and does not expect, any state change on the origin server as a result of applying a safe method to a target resource. Likewise, reasonable use of a safe method is not expected to cause any harm, loss of property, or unusual burden on the origin server. See RFC7231§4.2.1 for more details.
let is_cacheable: standard => bool;Request methods can be defined as "cacheable" to indicate that responses to them are allowed to be stored for future reuse. See RFC7234 for more details.
let is_idempotent: standard => bool;A request method is considered "idempotent" if the intended effect on the server of multiple identical requests with that method is the same as the effect for a single such request. Of the request methods defined by this specification, PUT, DELETE, and safe request methods are idempotent. See RFC7231§4.2.2 for more details.