Bug#212330: Feature question: port number in case of self refeering
Package: apache
Version: 1.3.27.1-3
Severity: wishlist
Hi,
We're using apache web servers in a quite complex configuration. Several
apache webservers are running on various servers and binded to various
tcp ports, like 8080. A firewall make a decision which apache and which
port the incoming traffic should be directed. This works nicely, however
we've got a problem. Eg URL like: http://www.something.com/example, (where
example is a directory for real) will cause to redirect browser to
http://www.something.com:8080/example/ which WILL NOT work, since 8080
is an internal-behind-the-firewall-only thing, and can't be accessed
from outside! My question is about the possibility to avoid this problem.
I can't find a solution with configuration options, so I must modify the
source to ALWAYS send back "normal tcp/80 port" whatever apache binds
to. But this is very ugly hack, and it is hard to upgrade binary only
distros of course, so I need to play with these from source and other
problems may occour as well. So it would be nice to have some configuation
possibility like this. Thanks in advance.
-- System Information:
Debian Release: testing/unstable
Architecture: i386
Kernel: Linux vega 2.6.0-test3 #1 Thu Aug 21 08:56:25 CEST 2003 i686
Locale: LANG=C, LC_CTYPE=C
Versions of packages apache depends on:
ii apache-common 1.3.27.1-3 Support files for all Apache webse
ii debconf 1.3.14 Debian configuration management sy
ii dpkg 1.10.15 Package maintenance system for Deb
ii libc6 2.3.2-8 GNU C Library: Shared libraries an
ii libdb4.1 4.1.25-6 Berkeley v4.1 Database Libraries [
ii libexpat1 1.95.6-6 XML parsing C library - runtime li
ii libmagic1 4.03-3 File type determination library us
ii logrotate 3.6.5-2 Log rotation utility
ii mime-support 3.23-1 MIME files 'mime.types' & 'mailcap
ii perl [perl5] 5.8.0-21 Larry Wall's Practical Extraction
-- debconf information excluded
Reply to: