Project

General

Profile

Bug #2844

mod_proxy strip out content-encoding gzip

Added by pabx06 5 months ago. Updated 5 months ago.

Status:
Invalid
Priority:
Normal
Assignee:
-
Category:
mod_proxy
Target version:
Start date:
2017-11-28
Due date:
% Done:

0%

Estimated time:
Missing in 1.5.x:

Description

troubleshooting mod_proxy . it removes the gzip content-encoding in the response from the backend:

BACK-END (Content-Encoding: gzip)

curl -H "Accept-Encoding: gzip" -I "http://192.168.0.66:8083/js/all.min.js" 
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 28 Nov 2017 04:19:16 GMT
Content-Type: application/javascript
Last-Modified: Mon, 27 Nov 2017 00:34:34 GMT
Connection: keep-alive
Vary: Accept-Encoding
ETag: W/"5a1b5d9a-28bee" 
Content-Encoding: gzip

FRONTEND lighttpd proxy (strip content encoding gzip)

curl -H "Accept-Encoding: gzip" -I "http://testwww.host.com/js/all.min.js" 
HTTP/1.1 200 OK
Server: nginx/1.10.3 (Ubuntu)
Date: Tue, 28 Nov 2017 04:26:27 GMT
Content-Type: application/javascript
Content-Length: 166894
Last-Modified: Mon, 27 Nov 2017 00:34:34 GMT
Vary: Accept-Encoding
ETag: "5a1b5d9a-28bee" 
Accept-Ranges: bytes

cat /etc/lighttpd/hosts/test.host.com.conf


$HTTP["host"] == "www.test.host.com" {
   url.redirect=("" =>"http://testwww.host.com")
}

$HTTP["host"] =~ "^testwww\.host\.com$" {
   proxy.server = ( "" => (("host" => "192.168.0.66", "port" => 8083 )))

}

root@ubuntu-desktop:/tmp# dpkg -l|grep lighttp
ii  lighttpd                                              1.4.33-1+nmu2ubuntu2                                amd64        fast webserver with minimal memory footprint
ii  lighttpd-mod-magnet                                   1.4.33-1+nmu2ubuntu2                                amd64        control the request handling module for lighttpd

History

#1

Updated by gstrauss 5 months ago

  • Status changed from New to Invalid

Hi. It's 2017. Why are you still running lighttpd 1.4.33, released Sep 2013, over 4 years ago?
The latest version of lighttpd is lighttpd 1.4.48 and it does not have this bug.

Also available in: Atom