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

Byte based offsets (file handler) #4

Open
joamag opened this issue Jun 20, 2012 · 1 comment
Open

Byte based offsets (file handler) #4

joamag opened this issue Jun 20, 2012 · 1 comment
Assignees
Milestone

Comments

@joamag
Copy link
Contributor

joamag commented Jun 20, 2012

Support for the byte based offsets.
This feature is also called byte serving.
There should be support for both single range and multi range byte serving.

Example

# request is made with these kind of headers
Range: bytes=500-999
Range: bytes=-500
Range: bytes=500-600,601-999

# response is created with these kind og headers
Content-Range: bytes 21010-47021/47022

Reference

http://en.wikipedia.org/wiki/Byte_serving
http://en.wikipedia.org/wiki/List_of_HTTP_header_fields#accept-ranges-response-header
http://www.web-polygraph.org/docs/userman/ranges.html
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.35
http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html#sec14.16

@ghost ghost assigned joamag Jun 20, 2012
@ghost ghost assigned joamag Oct 27, 2012
@joamag
Copy link
Contributor Author

joamag commented May 8, 2013

This feature is now partially implemented.
Multiple ranges are still missing. Must decide if they are meant to be implemented.

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

1 participant