New posts are disabled while we improve the user experience.

You can browse the site, or for urgent issues, raise a query at MyAccount.

question

Upvotes
Accepted
3 2 3 4

Support chunked transfer encoding

It looks like chunked transfer encoding isn't supported, since (at least for POST) requests, the Content-Length header is required for verifying the signature, which isn't present for chunked transfers. Is there a way to make chunked requests work?

(The reason for this is that our integration tests run behind a proxy that converts requests to chunked encoding)

Thanks!

apiworld-checkworld-check-onetransfer
icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

1 Answer

· Write an Answer
Upvotes
Accepted
3.1k 18 7 7

Hi @edo,

Yes, we do not support chucked transfer, at the moment. I will enter it as a request to consider going forward, however there hasn't been any interest in chuck transfer, until now.

Brian

icon clock
10 |1500

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.

Write an Answer

Hint: Notify or tag a user in this post by typing @username.

Up to 2 attachments (including images) can be used with a maximum of 512.0 KiB each and 1.0 MiB total.