Bug #1067: Content-Type header appears to be dropped [solved] - Lighttpd - lighty labs

Actions

Copy link

Bug #1067

closed

Content-Type header appears to be dropped [solved]

Added by Anonymous over 17 years ago. Updated over 15 years ago.

Status:

Fixed

Priority:

Normal

Category:

mod_proxy_backend_ajp13

Target version:

1.5.0

ASK QUESTIONS IN Forums:

Description

I found something that I think might be a bug in 1.5.0-r1691.

I was setting up lighttpd to proxy some requests to Jetty, but I noticed that the Content-Type headers that one of my servlets sets was getting lost at some point. After further examination of the packets being sent, I have determined that Jetty is sending the Content-Type header, but lighttpd must be dropping it. Also, other headers such as Location and Servlet-Engine seem to get lost.

I have attached an example of the AJP13 header response onto this ticket.

-- isomorphix

Files

Download all files

ajp13_header_response.raw (162 Bytes) ajp13_header_response.raw	AJP13 Header Response -- ismoprhix	Anonymous, 2007-03-03 14:18
mod_proxy_backend_ajp13.patch (445 Bytes) mod_proxy_backend_ajp13.patch	Fixes missing common AJP13 headers -- rush	Anonymous, 2007-09-13 16:55

Related issues 1 (0 open — 1 closed)

Actions

Copy link

Updated by Anonymous over 17 years ago

One other quick comment, other headers such as X-Test-Header go through just fine. The difference I can see being that in the AJP13 response the X-Test-Header is encoded as text and the other headers being blocked are the ones that get encoded as A0##.

-- ismorphix

Actions

Copy link

Updated by Anonymous about 17 years ago

Hi,
the problem is in src/mod_proxy_backend_ajp13.c on line 287

286: if (is_header && (len & AJP13_COMMON_HEADER_CODE)) {
287: p = keyvalue_get_value(response_headers, len);
288: if(p) len = strlen(p);
289: }

It's looking for key including AJP13_COMMON_HEADER_CODE which is 0xA000. I fixed it masking the upper byte like this: len & 0x00FF. Now it's working as expected. ;-) I also attached patch for this bug (mod_proxy_backend_ajp13.patch). Thank you for lighttpd. I love it! ;-)

-- rush

Actions

Copy link