Netscaler Response Headers Corrupted

Netscaler Response Headers Corrupted

book

Article ID: CTX227858

calendar_today

Updated On:

Description

Netscaler corrupts the Compression header (content encoding) when the response is beyond certain size of data and is specific to certain user agents(Huawei mobile in this particular case)

On the CS VIP level compression policy is bound. Then the request goes to LB VIP where the Header rewrite policy is bound.
When the request reaches the Client on Huawei devices the Content-Encoding header is corrupted and it comes as PContent-Encoding(P is taken from Pragma) or EContent-Encoding.

HTTP headers can be corrupted by the following series of events:
* The rewrite feature inserts an end-of-header mark, but the next packet contains more header bytes.
* The compression (CMP) feature interprets the incorrectly marked HTTP header-end as the actual end of the header, and tries to insert a content-encoding header.

This issue is addressed in issue id# 0691308

Issue/Introduction

Netscaler is corrupting the Content-Encoding header when we access the website through Netscaler CS VIP.