@neskemiquel This was fixed in version 1.41. It was a content-type issue.