[f-nsp] serveriron http on ports other than 80

[Bulger, Tim]

This is not correct..  The format to pass host information is like this:

 port http url "HEAD /home/home.jsp HTTP/1.1\r\nHost: www.whatever.com"



-----Original Message-----
From: alan [mailto:alan at ic24.net] 
Sent: Wednesday, January 08, 2003 2:21 AM
To: burnside at kattare.com; Bill McCaffrey
Cc: foundry-nsp at puck.nether.net
Subject: Re: [f-nsp] serveriron http on ports other than 80


You have a bit of a problem with virtual hosts on the foundrys. They
only support health checks in http 1.0 this means there is no real way
to pass a host header via a health check.

this means you will have to run multiple instances of apache on the
server and bind them to different ports. If you use virtual hosts the
serveriron will not send a host header so you get a 404 from the web
server indicating the site was not found\configured.

the unusual thing is the serveriron does support virtual host slb. this
will allow you to use a single virtual ip address and look for the host
header coming in and send it to an apache instance running on a high
port number.

one other thing to note. if you health check at layer 7 or script heal
check then the foundry sets everthing as positive by default once a
layer 4 healcheck has been achieved ( 404 error will mark a server as up
as the layer 4 healthcheck was passed ) you need to set server
no-fast-bringup this will enable layer 7 health checks.

same also applies to scripted healthchecks you need an entry of down
default.

one last thing (sorry for the rabit) layer 7 slb can be very unforgiving
to the serveriron check the cpu levels

I the configurations of a working setup if you're interested

Alan


----- Original Message -----
From: <burnside at kattare.com>
To: "Bill McCaffrey" <bill at neopets.com>
Cc: <foundry-nsp at puck.nether.net>
Sent: Thursday, December 05, 2002 11:10 AM
Subject: [f-nsp] serveriron http on ports other than 80


> Greetings,
>
>     I'm running several instances of Apache per server.  Many of them 
> on ports above 1024.  (so that normal users can start/stop them.)  Two

> issues I've run into:
>
>     I've tried configuring TCP health checks on the high ports (10000,

> 10010, etc.) via the TCP/UDP port config and it seems to fail the 
> health checks  on the real server every time.  (and thus serves 
> nothing.)  If I connect directly to the servers on the high ports I 
> get the pages I
expect.
>
>     The second issue is that I cannot bind from a low point to a high 
> point.  I was kind of hoping to be able to bind port 80 on the virtual

> server to port 10000 (or whatever) on the real server.  This is 
> necessary because right now I use apache on port 80 to proxy up to 
> port 10000 (or whatever) on the individual webservers.  So... if the 
> health checks just check port 80, the proxy may be up just fine, but 
> the high port server may not be up.  Thus the client may see a "proxy 
> failure" page if the port 80 server is alive and the port 10000 server

> is dead.
>
>     Sorry about all the questions.  I just got this serveriron 
> recently and despite reading through most of the docs on the website, 
> there is still much I am having trouble figuring out.  ;-)
>
> Cheers,
>
> ~Ethan B.
>
> --------------------------
> Ethan Burnside - Founder
> Kattare Internet Services
> http://www.kattare.com
> --------------------------
>
> _______________________________________________
> foundry-nsp mailing list
> foundry-nsp at puck.nether.net 
> http://puck.nether.net/mailman/listinfo/foundry-nsp

_______________________________________________
foundry-nsp mailing list
foundry-nsp at puck.nether.net
http://puck.nether.net/mailman/listinfo/foundry-nsp