2790551 - Odata API call returns HTTP 411 error

An API call is made from the application and a response is received stating a HTTP 411 error

SuccessFactors Learning Management System (LMS) - All Supported Versions

Authorization and content type headers are put into the call, or call is built as per requirements, the error is then generated

The HTTP Error 411 is generated when a call is made that does not have the Content-Length header added to the request.

The reason why it works in some applications but not others, primarily Postman, is because it internally adds this header to the request. When you call it outside of Postman, this header is missing and we are not able to see any error in our logs because the error is thrown by Akamai, not the application. Akamai server is rejecting these requests before they reach the Application Server.

This can be tested by adding “origin-“ in the API URL like this:

https://origin-CUSTOMERNAME.plateau.com/learning/odatav4/public/..............................

odata, api, http 411, content-header, postman , KBA , LOD-SF-LMS , Learning Management System , LOD-SF-LMS-ODA , Web Services OData , Problem