Skip to content

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

Open
@ctkdev

Description

@ctkdev

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!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions