You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@httpd.apache.org by Lee Weng Kong <LW...@dsta.gov.sg> on 2005/07/21 09:20:36 UTC

[users@httpd] Problem with SSL request via Windows Network Load Balancer (WNLB)

Hi,
 
I'm using Apache HTTP Server 2.0.53. This is set-up on a machine with IP
131.42.1.4. 
 
Windows Network Load-Balancer is configured to use virtual IP 131.42.2.5
and currently only manages the IP 131.42.1.4 (i.e. it will direct all
requests only to 131.42.1.4).
 
I've also set up the SSL for Apache using the mod_ssl module.
 
Here's what I observed:
1) http://131.42.1.4 was ok, i.e. I could see the Apache homepage.
2) https://131.42.1.4 was ok.
3) http://131.42.2.5 was ok.
4) http://131.42.2.5:443 was ok. 443 is my port number for HTTPS
5) https://131.42.2.5 <https://131.42.2.5/>  was NOT ok. This gave a
"Page cannot be found" error.
 
Looking into the logs, the only thing suspicious that came up was in
access.log, which had these entries when I tried to access 5).
 
130.254.9.26 - - [21/Jul/2005:14:55:23 +0800] "\x80L\x01\x03\x01" 500
184
130.254.9.13 - - [21/Jul/2005:14:55:26 +0800] "\x80L\x01\x03\x01" 500
184
130.254.9.13 - - [21/Jul/2005:14:55:26 +0800] "\x80L\x01\x03\x01" 500
184
 
Anyone hit by this problem before. Any ideas what is wrong here?
 
Thanks!
 
 


This e-mail is intended only for the named addressee(s) and may contain confidential and/or privileged information. If you are not the named addressee (or have received this e-mail in error), please notify the sender immediately. The unauthorised use, disclosure, distribution or copying of the contents in this e-mail is prohibited. Thank you.


Re: [users@httpd] Problem with SSL request via Windows Network Load Balancer (WNLB)

Posted by Davide Bianchi <da...@onlyforfun.net>.
Lee Weng Kong wrote:
> 4) http://131.42.2.5:443 was ok. 443 is my port number for HTTPS

No, this is not "ok". If you can get an https page by using http,
it means that the system is not 'speaking https' but plain http.
And this lead to

> 5) https://131.42.2.5 <https://131.42.2.5/> was NOT ok.

of course, because the server can't understand the request since
it's encrypted.

> Anyone hit by this problem before. Any ideas what is wrong here?

Your load balancer doesn't handle https correctly.

Davide


---------------------------------------------------------------------
The official User-To-User support forum of the Apache HTTP Server Project.
See <URL:http://httpd.apache.org/userslist.html> for more info.
To unsubscribe, e-mail: users-unsubscribe@httpd.apache.org
   "   from the digest: users-digest-unsubscribe@httpd.apache.org
For additional commands, e-mail: users-help@httpd.apache.org