Re: [I] Support `Transfer-Encoding: chunked` responses in HttpStore [arrow-rs-object-store]

["mattijn (via GitHub)" <gi...@apache.org>]

mattijn commented on issue #340:
URL: https://github.com/apache/arrow-rs-object-store/issues/340#issuecomment-3335611750

   Hi @tustvold, we are struggling with the strict behaviour of `object-store` with failing retrievals when content-length header is missing from the response (see issue at: https://github.com/vega/vegafusion/issues/569). I raised an issue at jsDelivr detailing the situation (https://github.com/jsdelivr/jsdelivr/issues/18661) where my question is answered by stating:
   
   > I recommend updating the client code to correctly handle `Transfer-Encoding: chunked`. When done correctly, it provides the same level of consistency guarantee as checking the `Content-Length`.
   
   The answer also includes a reference to the http specification stating that clients must be able to parse and decode the chunked encoding. (source here: https://httpwg.org/specs/rfc9112.html#chunked.encoding).
   
   While recent versions of the http protocol don't rely on chunking, I hope we still can find a way to make `object-store` compliant as a http/1.1 client.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: github-unsubscribe@arrow.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org