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

Support for 206 Partial Content Responses when responding to Requests with Request Header "Range" #33

Open
ctkdev opened this issue Mar 24, 2016 · 0 comments

Comments

@ctkdev
Copy link

ctkdev commented Mar 24, 2016

This is more of a question about how to architect a solution when it appears that there is no direct way to expose the request headers to the configured serviceName on a resource in the DSL.

For example, if a GET request on /api/audio-streams/1 is sent to the restful api with the following format:

Accept:audio/*
Cache-Control:no-cache
Connection:keep-alive
Pragma:no-cache
Range:bytes=10626313-

And the expectation for a response to the client for the purposes of streaming the requested partial content is:

Accept-Ranges:bytes
Connection:Keep-Alive
Content-Length:13780501
Content-Range:bytes 10626313-24406813/24406814
Content-Type:audio/mp4
Date:Thu, 24 Mar 2016 14:35:25 GMT
ETag:"1746b1e-52249b809ab9a"
Keep-Alive:timeout=5, max=100
Last-Modified:Sat, 17 Oct 2015 09:41:39 GMT

What is the recommended manner in which to support partial content responses via the restful-api?

I will be working on adding this functionality, but wanted to see if the authors of the plugin or anyone else in the community has already tackled this issue.

Thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant