[
https://issues.apache.org/jira/browse/KNOX-3248?focusedWorklogId=1003013&page=com.atlassian.jira.plugin.system.issuetabpanels:worklog-tabpanel#worklog-1003013
]
ASF GitHub Bot logged work on KNOX-3248:
----------------------------------------
Author: ASF GitHub Bot
Created on: 02/Feb/26 12:38
Start Date: 02/Feb/26 12:38
Worklog Time Spent: 10m
Work Description: smolnar82 commented on PR #1143:
URL: https://github.com/apache/knox/pull/1143#issuecomment-3834881292
Hi @nileshrathi345 !
Thanks for your contribution. If I understood well, your change is driven by
the fact that upstream components may decompress the body without updating
headers, especially in HA or proxy chains (e.g. with NGNIX in place before
Knox).
The gzip signature check already exists for this reason and should be
authoritative. Therefore we should only construct a GzipCompressorInputStream
when the signature confirms gzip and eliminate the uncertainty with the header
(which may or may not be correct).
Is this correct?
Issue Time Tracking
-------------------
Worklog Id: (was: 1003013)
Time Spent: 20m (was: 10m)
> Knox Gateway + Livy HA mode gzip exception results in duplicated requests and
> unneeded failovers
> ------------------------------------------------------------------------------------------------
>
> Key: KNOX-3248
> URL: https://issues.apache.org/jira/browse/KNOX-3248
> Project: Apache Knox
> Issue Type: Improvement
> Affects Versions: 2.0.0
> Reporter: Nilesh Rathi
> Priority: Major
> Fix For: 2.1.0
>
> Time Spent: 20m
> Remaining Estimate: 0h
>
> While using Apache Knox as a gateway for Livy in a High Availability (HA)
> environment, a race condition/logic error occurs in the rewrite provider when
> Knox receives a 307 Temporary Redirect from a standby node.
> throws:{{{}{}}}
> {code:java}
> IOException: Input is not in the .gz format{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
