[ 
https://issues.apache.org/jira/browse/NIFI-12516?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17797289#comment-17797289
 ] 

ASF subversion and git services commented on NIFI-12516:
--------------------------------------------------------

Commit 231dbde4b30bfea5b711169fe6f125c9279ec450 in nifi's branch 
refs/heads/main from Mark Payne
[ https://gitbox.apache.org/repos/asf?p=nifi.git;h=231dbde4b3 ]

NIFI-12516 Corrected Cluster Replicated Response Headers for HTTP/2

The headers in the map that come back when replicating a request used to be in 
the case given; however they can be lowercased in the OkHttp Headers object 
when using HTTP/2 instead of HTTP/1.1. As a result, we need to ensure that we 
always use lower-case header names or check the map case-insensitive.

This closes #8163

Signed-off-by: David Handermann <exceptionfact...@apache.org>


> When clustered, View Content shows wrong content type, will not show formatted
> ------------------------------------------------------------------------------
>
>                 Key: NIFI-12516
>                 URL: https://issues.apache.org/jira/browse/NIFI-12516
>             Project: Apache NiFi
>          Issue Type: Bug
>          Components: Core Framework, Core UI
>    Affects Versions: 2.0.0-M1
>            Reporter: Mark Payne
>            Assignee: Mark Payne
>            Priority: Major
>             Fix For: 2.0.0
>
>          Time Spent: 20m
>  Remaining Estimate: 0h
>
> When I choose to view a FlowFile's contents in the UI (regardless of whether 
> it came from Provenance view or List Queue view), it shows the content. 
> However, it shows the filename as an empty string, and it shows the 
> content-type as "text/plain" even though the mime.type attribute is set to 
> "application/json". As a result, when I try to change to use 'formatted' view 
> as, instead of 'original' it does not render it as JSON, since it thinks the 
> data is text/plain.



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

Reply via email to