- 11 Jul 2024
- 1 Minute to read
- Print
- PDF
HTTP Methods
- Updated on 11 Jul 2024
- 1 Minute to read
- Print
- PDF
Overview
The HTTP Methods rule sets the HTTP methods available to clients, to enable a client payload, and to set the maximum payload size (in bytes).
Configure the Rule
Here, we'll describe how to configure the rule with the Delivery Service Management UI.
API Users may choose to build the site configuration offline.
To configure an HTTP Methods rule:
- Navigate to the Select Rule dialog.
- In the Select Rule dialog, choose HTTP Methods.
- Set the rule attributes.
- From the Allow Methods dropdown, select/unselect the relevant methods.
Note: When the POST method is enabled, POST requests are not stored in the CDN's cache. They are proxied to the origin server for handling.
- Toggle Allow Client Payload On or Off to enable or disable the acceptance of payloads with incoming requests.
- Set the Max Payload Size, in bytes.
- Choose Add Rule.
SVTA Component: QW.HTTPMethodsACL
When you save the configuration version, the QW.HTTPMethodsACL component is added to the JSON configuration.
This is a private feature developed by Qwilt. In the JSON format, private features are nested within the MI.PrivateFeaturesList object, in the "generic-metadata-value" "features" field.
This example enables the GET, POST, and PUT methods; it allows a client payload of up to ten million bytes:
{
"generic-metadata-type": "MI.PrivateFeatureList",
"generic-metadata-value": {
"features": [
{
"feature-oid": "Qwilt",
"feature-type": "QW.HttpMethodsAcl",
"feature-value": {
"allowed-methods": [
"GET",
"POST",
"PUT"
],
"allow-client-payload": true,
"client-payload-max-size": 10000000
}
}
]
}
}
Attribute | Valid Values |
---|---|
allowed-methods | POST, PUT, GET, DELETE, OPTIONS, HEAD (Note that POST requests are proxied to the origin server for handling.) |
allow-client-payload | true, false |
client-payload-max-size | any integer (bytes) |