[ https://issues.apache.org/jira/browse/NIFI-11629?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17728784#comment-17728784 ]
ASF subversion and git services commented on NIFI-11629: -------------------------------------------------------- Commit ec525b0437f6369a7dca56b9818475385d0d03a6 in nifi's branch refs/heads/main from David Handermann [ https://gitbox.apache.org/repos/asf?p=nifi.git;h=ec525b0437 ] NIFI-11629 This closes #7327. Added Socket Write Timeout to InvokeHTTP Signed-off-by: Joe Witt <joew...@apache.org> > Add Socket Write Timeout to InvokeHTTP > -------------------------------------- > > Key: NIFI-11629 > URL: https://issues.apache.org/jira/browse/NIFI-11629 > Project: Apache NiFi > Issue Type: Improvement > Components: Extensions > Reporter: David Handermann > Assignee: David Handermann > Priority: Minor > Fix For: 1.latest, 2.latest > > Time Spent: 10m > Remaining Estimate: 0h > > The InvokeHTTP Processor relies on OkHttp to handle HTTP requests and > responses. InvokeHTTP includes a {{Socket Connect Timeout}} property to > control the timeout for initial connection attempts, and it includes a > {{Socket Read Timeout}} property to control the timeout for reading response > information from the remote HTTP server. > The OkHttp library also supports a > [writeTimeout|https://square.github.io/okhttp/4.x/okhttp/okhttp3/-ok-http-client/-builder/write-timeout/] > property to control the timeout for individual socket write operations. The > default write timeout is 10 seconds, which is sufficient for many scenarios, > but when sending large requests over a slow connection, 10 seconds may not be > sufficient. Adding a new Socket Write Timeout property to InvokeHTTP enables > support for these scenarios. -- This message was sent by Atlassian Jira (v8.20.10#820010)