Hello,
we will use pound for loadbalancing a handful of apache webservers.
We now started porting one webserver to pound. So pound gets the
official ip address of the webserver
and has two listeners on this ip, http and https.
Here is our constellation:
----------- --------- --------
| Client PC | | Pound | | Apache |
| | -- 1. --> | 2.3.2-2 | -- 2. --> | 2.0.52 |
----------- --------- --------
1. get https://www.server.com
2. get /
And here is the pound configuration:
User "nobody"
Group "nobody"
RootJail "/usr/share/pound"
Control "/var/run/pound/ctl_socket"
# syslog facility, see /etc/syslog.conf
LogFacility local5
# apache combined like log format - with service and backend
LogLevel 5
# close connection if client doesnt send anything for this period
Client 60
# how long pound will wait for response from the backend server
TimeOut 120
ListenHTTP
Address 1.1.1.1
Port 80
xHTTP 1
Service
BackEnd
Address 192.168.1.1
Port 80
End
Session
Type BASIC
TTL 3600
End
End
End
ListenHTTPS
Address 1.1.1.1
Port 443
Cert "/usr/share/ssl/certs/server.com.pem"
Ciphers
"ALL:!ADH:!EXPORT56:RC4+RSA:+HIGH:+MEDIUM:+LOW:+SSLv2:+EXP:+eNULL"
xHTTP 1
Service
BackEnd
Address 192.168.1.1
Port 80
End
Session
Type BASIC
TTL 3600
End
End
End
The redirection works fine, but if the user (client pc) requests a
directory name without the trailing slash,
e.g. https://www.server.com/test the
apache redirects to the same url
but with the trailing slash.
At this time the client pc is redirected to http://www.server.com/test/.
As you can see, the protocol changed from https to http. We didn't
purpose this behavior.
The apache webserver is configured with UseCanonicalName Off.
What else can we check? Can Pound fix the protocol change?
Thanks for your help
Matthias Pueschel
Germany
|