I found akka-http automatically induces Charset for some Media types. For example, a request of "text/plain" somehow becomes "text/plain; charset=UTF-8" in the server-side. This makes S3 Authorization scheme broken.
As far as I see the code, I couldn't realize it's a bug of akka-http nor couldn't find a code to fix this issue. So for some period as a workaround, I will choose to go with computing w/ and wo charset so to be free from this akka-http's ununderstandable behavior.
Now define Content-Type = MediaType; Charset
I found akka-http automatically induces Charset for some Media types. For example, a request of "text/plain" somehow becomes "text/plain; charset=UTF-8" in the server-side. This makes S3 Authorization scheme broken.
As far as I see the code, I couldn't realize it's a bug of akka-http nor couldn't find a code to fix this issue. So for some period as a workaround, I will choose to go with computing w/ and wo charset so to be free from this akka-http's ununderstandable behavior.