Closed yohanboniface closed 7 years ago
Encountered the same error, the problem in my case was in Content-Type
header which I was setting explicitly on the client side. Related StackOverflow question
tldr: Do not set Content-Type
header on the client side.