Skip to content

Conversation

@bneradt
Copy link
Contributor

@bneradt bneradt commented Nov 17, 2025

When an origin server returns Transfer-Encoding:chunked, ATS removes
this header during response processing to handle dechunking. This
prevented the original header value from being logged via
%<{Transfer-Encoding}ssh>. This fix stores the original
Transfer-Encoding value before deletion and uses the stored value if
requested via the ssh field.

Fixes: #6261

@bneradt bneradt added this to the 10.2.0 milestone Nov 17, 2025
@bneradt bneradt self-assigned this Nov 17, 2025
When an origin server returns Transfer-Encoding:chunked, ATS removes
this header during response processing to handle dechunking. This
prevented the original header value from being logged via
%<{Transfer-Encoding}ssh>. This fix stores the original
Transfer-Encoding value before deletion and uses the stored value if
requested via the ssh field.

Fixes: apache#6261
@bneradt bneradt force-pushed the log_transfer_encoding_chunked branch from f508f74 to 9e6a806 Compare November 17, 2025 18:26
@bryancall bryancall requested a review from masaori335 November 17, 2025 22:40
@bryancall bryancall added the Bug label Nov 17, 2025
bool trust_response_cl = false;
ResponseError_t response_error = ResponseError_t::NO_RESPONSE_HEADER_ERROR;
bool extension_method = false;
std::string server_response_transfer_encoding; ///< Storage for logging.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

IIUC, current.server->transfer_encoding stores the type of Transfer-Encoding. De we really need copy of the header here?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Cannot log Transfer-Encoding:chunked from origin

3 participants