Bug 49921 - Trailers in chunked http requests are not handled correctly
Summary: Trailers in chunked http requests are not handled correctly
Status: RESOLVED LATER
Alias: None
Product: Apache httpd-2
Classification: Unclassified
Component: mod_proxy_ajp (show other bugs)
Version: 2.2.16
Hardware: All All
: P2 normal with 2 votes (vote)
Target Milestone: ---
Assignee: Apache HTTPD Bugs Mailing List
URL:
Keywords: MassUpdate
Depends on:
Blocks:
 
Reported: 2010-09-13 22:34 UTC by Dan Luca
Modified: 2018-11-07 21:09 UTC (History)
0 users



Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dan Luca 2010-09-13 22:34:35 UTC
I'm having Apache web server (latest version - 2.2) connected to a Tomcat (also latest version - 6.0.29) server through the mod_proxy_ajp module. The Tomcat server hosts a spring 3.0 based application.
 
The clients of this application are embedded devices that use HTTP/1.1 protocol and send chunked http requests to the server that include trailers as well.
The application hosted by Tomcat does not see any of those trailers, I was expecting to find them as additional headers (per RFC 2616, 14.40) in the http request object. 
There are no messages in the Apache's error log file.
 
It seems like Apache web server does not support trailers handling on http requests (I know for sure Tomcat does not support it).
 
Here is a sample chunked http request to give you an idea:
=================================================================
POST /controller HTTP/1.1
Host: localhost
Content-Type: application/x-www-form-urlencoded; charset=ISO-8859-1
Transfer-Encoding: chunked
TE: chunked
Trailer: x-Content-Signature
 
358
<request body - first chunk>
240
<request body - last chunk>
0
x-Content-Signature: <signature>
=================================================================

The "x-Content-Signature" trailer does not get transferred into the request headers. 

Thanks,
Dan Luca.
Comment 1 William A. Rowe Jr. 2018-11-07 21:09:09 UTC
Please help us to refine our list of open and current defects; this is a mass update of old and inactive Bugzilla reports which reflect user error, already resolved defects, and still-existing defects in httpd.

As repeatedly announced, the Apache HTTP Server Project has discontinued all development and patch review of the 2.2.x series of releases. The final release 2.2.34 was published in July 2017, and no further evaluation of bug reports or security risks will be considered or published for 2.2.x releases. All reports older than 2.4.x have been updated to status RESOLVED/LATER; no further action is expected unless the report still applies to a current version of httpd.

If your report represented a question or confusion about how to use an httpd feature, an unexpected server behavior, problems building or installing httpd, or working with an external component (a third party module, browser etc.) we ask you to start by bringing your question to the User Support and Discussion mailing list, see [https://httpd.apache.org/lists.html#http-users] for details. Include a link to this Bugzilla report for completeness with your question.

If your report was clearly a defect in httpd or a feature request, we ask that you retest using a modern httpd release (2.4.33 or later) released in the past year. If it can be reproduced, please reopen this bug and change the Version field above to the httpd version you have reconfirmed with.

Your help in identifying defects or enhancements still applicable to the current httpd server software release is greatly appreciated.