Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Feature Request: Support chucked data streams to better support HTTP1.1 clients #1637

Open
GeorgeKerwood opened this issue Aug 24, 2021 · 5 comments

Comments

@GeorgeKerwood
Copy link

Firstly, many congratulation on, and thanks for, your fantastic project! It's been a great help to me and I much enjoyed the book which has improved invaluable alongside.

I would humbly request that you consider supporting the chunked transfer encoding of http 1.1 client streams. I have recently completed a project deploying WiFiNina on an Arduino Nano 33 IoT which integrates a NINA W-102 WiFi. Since the library does not support http 1.0 degradation, a very large part of the work effort was preparing various REST API responses to "load" the JSON content to buffers prior to deserialization.

Many Thanks,

George

@GeorgeKerwood GeorgeKerwood changed the title Feature Request: Support chucked data streams to be better support HTTP1.1 clients Feature Request: Support chucked data streams to better support HTTP1.1 clients Aug 24, 2021
@bblanchon
Copy link
Owner

Hi George,

I will add a new decorator in the StreamUtils library, but I'm very busy at the moment, so I cannot give any ETA.

When you say "the library does not support http 1.0 degradation", which library are you talking about?

Best regards,
Benoit

@GeorgeKerwood
Copy link
Author

Salut!

Thanks for the reply. Great, no particular hurry, my project is concluded for the time being I'd just thought it would make a useful addition.

"The library" in this case was WiFiNina. Unless of course it was just that I couldn't discover how to do so. A further caveat had been that Postman, which I had been using to prepare and test my requests, also does not support http 1.0 so the debugging/testing on the embedded side would of been considerable longer with that limitation.

Your hard work is apricated, Best Regards,
George

@bblanchon
Copy link
Owner

Hi George,

As far as I can see, WiFiNina only works at TCP/UDP level and doesn't provide any HTTP abstraction.
I don't see how it could force you to use HTTP 1.1.

Best regards,
Benoit

@GeorgeKerwood
Copy link
Author

Hi Benoit,

You're right. In my inexperience I misdiagnosed the "http 1.0 isn't working" problem as WiFiNina problem and not an endpoint problem (which I now think it is). I'll take another look to see if I can't remove the need for preloading buffer arrays.

Thanks for the input,

George

@bblanchon
Copy link
Owner

Hi George,

I never saw a server that refuses to downgrade to HTTP 1.0.
Please let me know if that’s your case.

Best regards,
Benoit

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants