You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@impala.apache.org by "Thomas Tauber-Marshall (Jira)" <ji...@apache.org> on 2019/08/21 14:51:00 UTC
[jira] [Resolved] (IMPALA-8869) Fix handling of HTTP keep-alive
when returning 401
[ https://issues.apache.org/jira/browse/IMPALA-8869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Thomas Tauber-Marshall resolved IMPALA-8869.
--------------------------------------------
Fix Version/s: Impala 3.4.0
Resolution: Fixed
> Fix handling of HTTP keep-alive when returning 401
> --------------------------------------------------
>
> Key: IMPALA-8869
> URL: https://issues.apache.org/jira/browse/IMPALA-8869
> Project: IMPALA
> Issue Type: Bug
> Components: Clients
> Affects Versions: Impala 3.3.0
> Reporter: Thomas Tauber-Marshall
> Assignee: Thomas Tauber-Marshall
> Priority: Blocker
> Fix For: Impala 3.4.0
>
>
> Recent work has added support for HTTP authentication both for the thrift hs2 interface and for the webserver. In both cases, we mishandle HTTP keep-alive semantics when returning a 401 to indicate an unauthorized request because we close the connection but don't return a "Connection: closed" header, which can cause clients to incorrectly believe that the connection has remained open.
--
This message was sent by Atlassian Jira
(v8.3.2#803003)