Bug#568519: lighttpd fails proxy connections when upgraded to 1.4.19-5+lenny1
Hi Stefan, I'm not using redmine; the problem impacts all documents including static documents on the lighttpd side. Access directly to lighttpd directly from web browsers appears to work with the several I've tried. The only failures I've encountered are when reverse-proxying through apache and it fails with all web browsers in said configuration. This fails 100% of the time when attempted with lighttpd 1.4.19.5+lenny1 and various releases of apache 2.2. I do not recall seeing any log entries on the Lighttpd side. The log entries on the apache side are in the bug ticket. I'm using this directive in a .htaccess file on the apache side to trigger the reverse proxy: RewriteRule ^https/([^\/]+)/(.*)$ https://$1/$2 [P] I then point a web browser to: http://apache.server/directory/https/192.168.1.1/lighttpd.file Worked fine with no configuration changes on either side in lighttpd 1.4.19.5. If for some reason apache actually works with lighttpd when you try to repeat the described behavior, please send me the configs you used. I'll be happy to chase it further and narrow it down. Regards, Bill Herrin -- William D. Herrin her...@dirtside.com b...@herrin.us 3005 Crane Dr. .. Web: http://bill.herrin.us/ Falls Church, VA 22042-3004 -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568519: lighttpd fails proxy connections when upgraded to 1.4.19-5+lenny1
Hi, you both didn't describe the lighttpd side of your configuration; and you didn't mention anything else like: * does redmine still work when you connect to lighttpd directly (test with curl -v please) * is there anything in the error.log/access.log of lighty? So you should paste a little bit more details. -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#568519: lighttpd fails proxy connections when upgraded to 1.4.19-5+lenny1
Package: lighttpd Version: 1.4.19-5+lenny1 Severity: normal After upgrading lighttpd to 1.4.19+lenny1 I found that the apache server that forwards one of its directories (hereafter referred to as /proxydir/) to the machine in question via the proxy module of apache can no longer serve requests to that directory. The message in the apache log is: Fri Feb 05 12:11:01 2010] [error] [client 123.45.67.89] (70014)End of file found: proxy: error reading status line from remote server lighttpd-running-server.mydomain.de [Fri Feb 05 12:11:01 2010] [error] [client 123.45.67.89] proxy: Error reading from remote server returned by /proxydir/ The same proxy setup (without any change on the apache side) works when I downgrade to 1.4.19-5. The setup of the apache server is as described in http://www.redmine.org/wiki/redmine/HowTo_Install_Redmine_in_a_sub-URI#With-a-reverse-proxy Greetings, Thomas Jahns -- System Information: Debian Release: 5.0.4 APT prefers stable APT policy: (500, 'stable') Architecture: i386 (i686) Kernel: Linux 2.6.30-bpo.2-686 (SMP w/1 CPU core) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/bash Versions of packages lighttpd depends on: ii libattr1 1:2.4.43-2Extended attribute shared library ii libbz2-1.0 1.0.5-1 high-quality block-sorting file co ii libc6 2.7-18lenny2 GNU C Library: Shared libraries ii libfam02.7.0-13.3+lenny1 Client library to control the FAM ii libldap-2.4-2 2.4.11-1+lenny1 OpenLDAP libraries ii libpcre3 7.6-2.1 Perl 5 Compatible Regular Expressi ii libssl0.9.80.9.8g-15+lenny6 SSL shared libraries ii libterm-readline-perl- 1.0302-1 Perl implementation of Readline li ii lsb-base 3.2-20Linux Standard Base 3.2 init scrip ii mime-support 3.44-1MIME files 'mime.types' 'mailcap ii zlib1g 1:1.2.3.3.dfsg-12 compression library - runtime lighttpd recommends no packages. Versions of packages lighttpd suggests: pn apache2-utils none (no description available) ii openssl 0.9.8g-15+lenny6 Secure Socket Layer (SSL) binary a pn rrdtool none (no description available) -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
