New HTTP Library Issue

Michael Scott

Hello Jukka / Paul,

We are using the legacy HTTP API's current and include a "Content-Length:" header field to denote the amount of data in the payload.

The new API is completely broken when including the Content-Length header field, as the payload is sent in a chunked format which prepends the byte count to each "chunk".  This means that the user's Content-Length value is now invalid.

I'm not really sure how to solve this issue in the new API.. I don't think we should be changing the payload of the message w/o the user opting in or knowing about it.

I can get our code running on the new API if I comment out the chunked insertion logic and apply the HTTP lib payload patch here:

- Mike

Join to automatically receive all group messages.