By default, Akamai honors GET, HEAD, and OPTIONS requests to your origin. Include this behavior to allow HTTP requests using the POST method.
How it works
When set to Allow, POST 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 POST requests to this property with a 403 Forbidden response.
Features and options
You can also decide whether to allow POST calls without a Content-Length header.
What it does
Allows or denies the HTTP requests using the POST method.
Allow POST without Content-Length header
By default, POST requests require a Content-Length header, or they result in a 411 error. The error occurs even if the POST request doesn’t contain a body and theoretically shouldn’t require Content-Length header. If you enable this option and don’t specify the Content-Length, the edge server will look for a Transfer-Encoding header to determine how to chunk the data. If neither header is present, the server assumes the request has no body, and it adds a header with a 0 value to the forward request.
If you enable this, it also applies to instances of the Allow PATCH and Allow PUT behaviors in the same rule tree. PUT and PATCH requests to your property won't require a Content-Length header.