You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Some request implementations in other languages work slightly differently: they first return a Response containing HTTP status and headers, after which the user initiates reading.
you can pipe the IO into a JSON/CSV/JPEG/MP3/etc parser, depending on the Content-Type header of the response.
you can choose not to read the response body depending on the headers (I'm thinking of cache headers)
I also think this is a "feature" of HTTP: HTTP status and headers are received first, describing how to remaining body should be read.
Is this behaviour already possible with Downloads.request? I have the impression that right now, request will first write the full body content into the given output::IO, and then it returns the Response object containing headers and such.
Thanks for the awesome package!
The text was updated successfully, but these errors were encountered:
Some
request
implementations in other languages work slightly differently: they first return aResponse
containing HTTP status and headers, after which the user initiates reading.fetch
in JSrequests
in Python3What this enables is:
Content-Type
header of the response.I also think this is a "feature" of HTTP: HTTP status and headers are received first, describing how to remaining body should be read.
Is this behaviour already possible with
Downloads.request
? I have the impression that right now,request
will first write the full body content into the givenoutput::IO
, and then it returns theResponse
object containing headers and such.Thanks for the awesome package!
The text was updated successfully, but these errors were encountered: