[ 
https://issues.apache.org/jira/browse/NIFI-13652?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Matt Gilman updated NIFI-13652:
-------------------------------
    Fix Version/s: 2.0.0-M5
       Resolution: Fixed
           Status: Resolved  (was: Patch Available)

> Add HTTP Range Header Handling for Content Download
> ---------------------------------------------------
>
>                 Key: NIFI-13652
>                 URL: https://issues.apache.org/jira/browse/NIFI-13652
>             Project: Apache NiFi
>          Issue Type: New Feature
>          Components: Core Framework
>            Reporter: David Handermann
>            Assignee: David Handermann
>            Priority: Major
>             Fix For: 2.0.0-M5
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> The framework REST API supports several methods for downloading FlowFile 
> content associated with queues and provenance events. Content Viewer 
> capabilities such as a hexadecimal representation can make use of partial 
> content retrieval to show the first selected number of bytes.
> [RFC 9110|https://httpwg.org/specs/rfc9110.html] defines HTTP Semantics and 
> Section 14 describes request and response headers for ranges of bytes. The 
> content download REST API resource methods should be enhanced to support 
> partial content retrieval using the {{Range}} Header as an optional 
> parameter. Existing response content should remain unchanged. When processing 
> requests with a {{Range}} header, resource methods should return HTTP 206 
> Partial Content as the response status.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to