As we previously mentioned, several changes are being made to our API platform, one of which is that all HTTP headers are now case-insensitive and written in lowercase.
This change specifically affects, for example, the POST method for /ecs/ppl/myapi2/shipment/batch in the case of the "Location" header in the response. It will now be written entirely in lowercase, i.e., "location".
Based on our experience with implementations, we have found that many customers have configured their header-reading logic incorrectly. When creating a batch in the response, they search for the "Location" header; in such cases, they do not find the "location" header, even though it refers to the same object in the response. Unfortunately, the implementation of the HTTP2 protocol, which we are preparing to introduce with this change, strictly enforces lowercase headers; as a result, with this incorrect client-side implementation, the header cannot be found and the API integration does not work.
We therefore ask that you review this part of your integration and ensure that your solution is ready for this change; otherwise, it may stop working. If your implementation is not ready for this change, you will need to modify it—we are unable to influence this behavior on our end.
You can verify the correct behavior in the sandbox environment by sending a POST request to https://x-api-sandbox.dhl.com/ecs/ppl/myapi2/shipment/batch. We apologize for any inconvenience and thank you for your understanding and cooperation. We are confident that together we will successfully navigate this.