You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@nifi.apache.org by "David Handermann (Jira)" <ji...@apache.org> on 2021/02/08 20:57:00 UTC
[jira] [Resolved] (NIFI-8181) Allow users to specify which HTTP
Protocol(s) to use with InvokeHTTP
[ https://issues.apache.org/jira/browse/NIFI-8181?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Handermann resolved NIFI-8181.
------------------------------------
Fix Version/s: 1.14.0
Resolution: Fixed
PR includes update to OkHttp 4.9.0 in nifi-standard-bundle.
> Allow users to specify which HTTP Protocol(s) to use with InvokeHTTP
> --------------------------------------------------------------------
>
> Key: NIFI-8181
> URL: https://issues.apache.org/jira/browse/NIFI-8181
> Project: Apache NiFi
> Issue Type: Improvement
> Components: Extensions
> Affects Versions: 1.12.1
> Reporter: Mark Payne
> Assignee: Nathan Gough
> Priority: Major
> Fix For: 1.14.0
>
> Time Spent: 2h 20m
> Remaining Estimate: 0h
>
> InvokeHTTP uses the OkHttp client. The client allows users to specify which HTTP Protocols should be allowed, but currently that is not exposed as a property in InvokeHTTP. As a result, some NiFi users are encountering issues when interacting with certain servers using HTTP 2. We should allow for explicitly setting the protocol to HTTP 1.1.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)