By default, Akamai honors GET, HEAD, and OPTIONS requests to your origin. Include this behavior to allow HTTP requests using the PUT method.
How it works
When set to Allow, PUT requests pass to the origin, but the content isn’t cached. When you don't specify this behavior set it to Deny, Akamai edge servers deny all PUT requests to this property with a 501
Not Implemented response.
You need a
PUT requests require a
Content-Length header, or they result in a
411 Length required error. The error occurs even if the PUT request doesn’t contain a body. If you enable Allow PUT, include this header with a request and indicate the size of the message body, in bytes. If the PUT request doesn't have a body, include the header and set it to
Features and options
|Field||What it does|
|Behavior||Allows or denies the HTTP requests using the PUT method.|
See the Allow DELETE, Allow PATCH, Allow POST, Allow OPTIONS behaviors.
Updated 3 days ago