Feature request: map appropriate HTTP request methods to update calls

What are your issues with streaming large files? Is it 206 partial responses? If so see this thread: Boundary node http response headers

Basically in the long run the platform should be able to provide partial response capabilities for us (through the boundary nodes), but once they allow Range headers to pass through the boundary node whitelist I have a fork of the certified-assets canister that implements range requests.

I’m waiting on this for podcast audio hosting on the IC to work better (though it works now if users download the podcasts).