Methods recognized (but not necessarily handled) by the server.
More...
Methods recognized (but not necessarily handled) by the server.
These constants are used in bit shifting masks of size int, so it is unsafe to have more methods than bits in an int. HEAD == M_GET. This list must be tracked by the list in http_protocol.c in routine ap_method_name_of().
◆ AP_METHOD_BIT
The method mask bit to shift for anding with a bitmask.
◆ M_BASELINE_CONTROL
#define M_BASELINE_CONTROL 24 |
◆ M_CHECKIN
◆ M_CHECKOUT
#define M_CHECKOUT 16 /* : */ |
◆ M_CONNECT
◆ M_COPY
◆ M_DELETE
◆ M_GET
#define M_GET 0 /** RFC 2616: HTTP */ |
◆ M_INVALID
Value:RFC 2324: HTCPCP/1.0 RFC 2324: HTCPCP/1.0
◆ M_LABEL
◆ M_LOCK
◆ M_MERGE
◆ M_MKACTIVITY
◆ M_MKCOL
◆ M_MKWORKSPACE
◆ M_MOVE
◆ M_OPTIONS
◆ M_PATCH
#define M_PATCH 7 /** RFC 5789: PATCH Method for HTTP */ |
◆ M_POST
◆ M_PROPFIND
#define M_PROPFIND 8 /** RFC 2518: WebDAV */ |
◆ M_PROPPATCH
#define M_PROPPATCH 9 /* : */ |
◆ M_PUT
◆ M_REPORT
◆ M_TRACE
#define M_TRACE 6 /** RFC 2616: HTTP */ |
◆ M_UNCHECKOUT
◆ M_UNLOCK
#define M_UNLOCK 14 /** RFC 2518: WebDAV */ |
◆ M_UPDATE
◆ M_VERSION_CONTROL
#define M_VERSION_CONTROL 15 /** RFC 3253: WebDAV Versioning */ |
◆ METHODS
METHODS needs to be equal to the number of bits we are using for limit masks.
◆ ap_method_list_t
◆ ap_method_mask_t
The type used for method masks.