By default, ​Akamai​ honors GET, HEAD, and OPTIONS requests to your origin. Include this behavior to allow HTTP requests using the PATCH method.

How it works

When set to Allow, PATCH requests pass to the origin, but the content isn’t cached. When you don't specify this behavior at all or set it to Deny, ​Akamai​ edge servers deny all PATCH requests to this property with a 501 Not Implemented response.

You need a Content-Length header

PATCH requests require a Content-Length header, or they result in a 411 Length required error. The error occurs even if the PATCH request doesn’t contain a body. If you enable Allow PATCH, include this header with a request and indicate the size of the message body, in bytes. If the PATCH request doesn't have a body, the header needs to be set to 0.

📘

If you don't want to include the Content-Length header with requests, you can add the Allow POST behavior to your rule and enable its Allow POST without Content-Length header option. This also enables this functionality for the Allow PATCH behavior.

Features and options

Related topics

See also the Allow DELETE, Allow OPTIONS, Allow POST, and Allow PUT behaviors.