You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@nifi.apache.org by "Peter Wicks (JIRA)" <ji...@apache.org> on 2019/07/25 18:50:00 UTC

[jira] [Commented] (NIFI-6473) Check Http Context Status Processor

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

Peter Wicks commented on NIFI-6473:
-----------------------------------

I've decided that this is actually not possible, due to the way HTTP works.  Given the lack of heart beats, and that per the HTTP spec the first line of an HTTP response MUST be the Status code.

Calling flushBuffer without writing content to an open connection still sends the status code and headers, locking them in and not allowing modification.

Closing as infeasible due to protocol constraints..

> Check Http Context Status Processor
> -----------------------------------
>
>                 Key: NIFI-6473
>                 URL: https://issues.apache.org/jira/browse/NIFI-6473
>             Project: Apache NiFi
>          Issue Type: Improvement
>          Components: Extensions
>    Affects Versions: 1.9.2
>            Reporter: Peter Wicks
>            Assignee: Peter Wicks
>            Priority: Minor
>
> In between a HandleHttpRequest and HandleHttpResponse a lot can happen. If the flow is long running it would be nice to know if the HTTP Context is still valid, or if the user terminated the connection.  This is especially useful before starting a long running process, or if a FlowFile has been queued for a long period of time.
> Suggest creating a "CheckHttpContext" Processor that will route FlowFile's to relationships such as "Valid" if the connection is still good, or "invalid"/"expired".



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)