-
Notifications
You must be signed in to change notification settings - Fork 15
Open
Description
First of all, nice work.
I spotted an issue with the loss of the Content Type within the AkkaHttpLambdaHandler.proxyToAkkaRequest method.
What happens.
- User makes a request with Content-Type set to 'application/json' (can be anything really).
- Code recreates the HttpRequest by using HttpEntity.apply on the body.
- The above step results in the below, which can show the loss of the content-type.
HttpEntity.Strict(text/plain; charset=UTF-8,{
"name": "ArmandoPadilla"
})
From the Akka-http perspective. This causes issues when using entity[as[JsValue]] which results in.
The request's Content-Type is not supported. Expected:
application/json
Metadata
Metadata
Assignees
Labels
No labels