[
https://issues.apache.org/jira/browse/NIFI-6342?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Diego Queiroz updated NIFI-6342:
--------------------------------
Description:
Hello guys.
I just updated my NiFi environment to the last available version and,
apparently, the bug reported in
[https://issues.apache.org/jira/projects/NIFI/issues/NIFI-5522] continues in
the last release (=1.9.2, Jetty = 9.4.11.v20180605).
I was confused if I should comment in the same thread or open a new ticket, so
sorry if I did wrong in opening a new issue.
Are there any thoughts about this? I really wasn't able to test in 1.8.0 where
this bug was supposed to be fixed, so I don't know if it wasn't fixed at all or
if it happened again in 1.9.2.
was:
Hello guys.
I just updated my NiFi environment to the last available version and,
apparently, the bug reported in
[https://issues.apache.org/jira/projects/NIFI/issues/NIFI-5522] continues in
the last release (=1.9.2, Jetty = 9.4.11.v20180605).
I was confused if I should comment in the same thread or open a new ticket, so
sorry if I did wrong in a new issue.
Are there any thoughts about this? I really wasn't able to test in 1.8.0 where
this bug was supposed to be fixed, so I don't know if it wasn't fixed at all or
if it happened again in 1.9.2.
> HandleHttpRequest enters in fault state and does not recover (regression)
> -------------------------------------------------------------------------
>
> Key: NIFI-6342
> URL: https://issues.apache.org/jira/browse/NIFI-6342
> Project: Apache NiFi
> Issue Type: Task
> Affects Versions: 1.9.2
> Reporter: Diego Queiroz
> Priority: Major
> Labels: security
>
> Hello guys.
> I just updated my NiFi environment to the last available version and,
> apparently, the bug reported in
> [https://issues.apache.org/jira/projects/NIFI/issues/NIFI-5522] continues in
> the last release (=1.9.2, Jetty = 9.4.11.v20180605).
> I was confused if I should comment in the same thread or open a new ticket,
> so sorry if I did wrong in opening a new issue.
> Are there any thoughts about this? I really wasn't able to test in 1.8.0
> where this bug was supposed to be fixed, so I don't know if it wasn't fixed
> at all or if it happened again in 1.9.2.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
