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
{{ message }}
This repository has been archived by the owner on Mar 12, 2020. It is now read-only.
Is your feature request related to a problem?
Sometimes it would be required for a gateway to return a specific range of bytes of the big file served eg. when we have a video or an audio and we would like to start playing it from a specific point of time. It will be possible due to accepting the Range HTTP headers in the requests and sending back the response with HTTP 206 with Content-Range header. I'm not really technical, but this is what might be needed in my understanding.
Describe the solution you'd like
The technical details are explained in the issue of another project here and there
Additional context
Raising this feature request as it was suggested by @andrewxhill and @carsonfarmer on Slack
The text was updated successfully, but these errors were encountered:
I think what is required to do is to redefine the reader in the DataAtPath function in ipfs/main.go line 50, with different reader which will accept range parameter.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Is your feature request related to a problem?
Sometimes it would be required for a gateway to return a specific range of bytes of the big file served eg. when we have a video or an audio and we would like to start playing it from a specific point of time. It will be possible due to accepting the
Range
HTTP headers in the requests and sending back the response withHTTP 206
withContent-Range
header. I'm not really technical, but this is what might be needed in my understanding.Describe the solution you'd like
The technical details are explained in the issue of another project here and there
Additional context
Raising this feature request as it was suggested by @andrewxhill and @carsonfarmer on Slack
The text was updated successfully, but these errors were encountered: