From: Maurice Ruckman <MRuckman@HollandAmericaGroup.com>
Date: Thursday, October 29, 2015 at 9:24 PM
To: Ruchika Bhartiya <RBhartiya@HollandAmerica.com>, Donald Tripp <DTripp@HollandAmerica.com>, "Franco, Mark (CarnCorp)" <MFranco@carnival.com>
Cc: Anila Augustine <AAugustine@HollandAmericaGroup.com>, "Bogh, Allan (HA Group Contractor)" <ABogh@HollandAmericaGroup.com>, "DCosta, John (HA Group)" <JDCosta@HollandAmericaGroup.com>
Subject: Re: Akamai config for put/post
Thanks for the help Ruchika and Don! Just to close the loop on this. The issue turned out to be sending a payload with a DELETE request. Here are the final notes from a meeting with Akamai.
On Oct 29, 2015, at 3:48 PM, Gupta, Diwaker <diwakg@akamai.com> wrote:
Thank you for your time over the phone. Recap of discussion over the phone :
- This issue is observed in the cases if the first request method is Delete , and contains a payload and the next requests uses the same persistent connection
- The latest HTTP RFC states that there are no defined semantics for payloads in DELETE requests (https://tools.ietf.org/html/rfc7231#page-29).
- It doesn’t specifically say they should be allowed or denied but mentions that a server may reject the request
- We don’t deny this requests. However the payload is added to the subsequent request causing the request to fail
- The fix will be to either remove delete payload, or deactivate persistent connection between Akamai and client for Delete method
- As discussed we can remove the payload from Delete , and will re run the tests to confirm if the issue is fixed.
