AnsweredAssumed Answered

http/s POST requests - how does Akamai process these?  Are there size limitations? Are they immediately forwarded?

Question asked by Matt Shannon on May 22, 2015
Latest reply on May 26, 2015 by Jeff McLean

Hi Akamai

 

I need to understand how Akamai handles incoming http/s POST requests.

 

Specifically, whether the POST request is immediately streamed/proxied to the Origin server? or whether Akamai first buffers the full payload from the client, before sending request across to the Origin?

 

Also does Akamai modify the payload transfer encoding in any way?  (for example from chunked to a fixed content length variant)

 

Are there also any size limitations (fixed length or chunking), and any timeout settings to be aware of?

 

We are running in to some strange issue with POST requests (triggered from our Web Service clients) failing once the payload starts exceeding approximately 1 gigabyte in size.

 

These web service requests have a soap envelope which includes a timestamp section.  The (origin) server will reject requests when clock skew occurs (5 minutes or more).

Thus unless Akamai immediately forwards the POST payload to the origin, this timestamp problem could potentially be hit were akamai consuming/buffering the full client payload before sending across to origin.

 

<wsu:Timestamp ... wsu:Id="Timestamp-q3iaQfUEUCusu1X0IvIClQ22">
   <wsu:Created>2015-02-05T15:28:38Z</wsu:Created>
   <wsu:Expires>2015-02-05T23:28:38Z</wsu:Expires>
</wsu:Timestamp></wsse:Security>
</env:Header>

I assume also from a best-practice perspective that we ideally would not be sending these big file POST requests via the CDN, and instead going to our origin server directly?

 

thanks

 

Matt Shannon / Oracle

Outcomes