• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Webserver <--> webserver routing

C

cirrus1

Senior member
I two webservers on my home network, which only have one connection to the internet via a proxy box (W2K with Sygate). Currently the proxy routes all webtraffic to the W2K box: A W2K with IIS5 (Fully patched) and a Linux with Apache (Big surprise 😉 Is it possible by urls let one of the servers decide what machine the traffic will go to. For example if the Linux box gets a request: http://mydomain/W2KBox/ it will route the traffic to another IP (In this case the W2K box) on the LAN

Or is this only possible with some advanced proxy/gateway?
 
I know that IIS has provisions for redirecting to content on another server. You could probably do the same via tweeking the Apache httpd.conf. But as for how it would display, I expect that some other port might need to be opened going out...? 😕

.
 
Where in the IIS configurations can this be done? It (almost) doesn't matter to me what server that does the redirecting. I would prefer the Apache if they both could do it (Simply because Linux rules when it comes to networking... 😀 )
 
you mean incoming traffic comes in, and if it's to http://domain.com/$foo then automatically pass to one server, otherwise send all traffic to the other server? I don't see an easy way to do that, besides having some whack front end doing http request handling. I work with web servers all day and can't think of a quick and dirty solution.

$.02
randal
 
hrm, just thought about it some more, and by far the easiest way to do it is with DNS and sub-domains.

i.e.
foo.domain.com -> 192.168.0.1
bar.domain.com -> 192.168.0.2

Then, any requests going in to bar.domain.com would automatically be sent to the computer that has that IP. That would work. Otherwise, you might want to consider simple redirects, or using virtual directories inside IIS.

$.02
randal
 
Well - it's a little different for IIS 5 as opposed to IIS 4, but there should be a configuration properties screen (I guess under that Manangement Console) where you can setup a reference to a &quot;virtual&quot; directory - which could be a directory on a different machine...

Now in your case, I have a feeling that you would probably need to also setup Samba on the linux box so the 2 machines can interconnect and have directory interaction.

I currently have my alpha running Red Hat 6.2, mounting an SMB share with my dual Xeon running 2K AS, to grab RC5 pproxy logs generated by the pproxy running on the 2K, for further processing by the ppstats program running on my alpha, with a display of the results via the alpha's Apache. I have IIS disabled (mainly because I use a port 80 pproxy and IIS running screws that up), but I'd have to really go through that console to show you exactly where it is. It was sortof easier to get to those screens (IMHO) with IIS 4, 😉
 
I'll look into and try both solutions. We'll see what works out hehe

Poof:

Actually it's RC5 &amp; OGR ppstats that I have running on the Linux box 🙂
 
hrm, just thought about it some more, and by far the easiest way to do it is with DNS and sub-domains.

i.e.
foo.domain.com -> 192.168.0.1
bar.domain.com -> 192.168.0.2


But if there's a firewall there with NAT running and the default port (ie., 80) is assumed, then you can only forward the request to one IP (machine) or the other.

However, you could possibly specify a different port in the redirect URL (meaning the user wouldn't have to explicitly type that port number in), and have it go back out and then come back in via a different forwarded port on the firewall, to the OTHER machine that has its web server listening on that different port.

So you could maybe have something like &quot;http://domain/default.htm&quot; (which comes in on port 80) and then &quot;default.htm&quot; redirects to &quot;http//domain:8080/default.htm&quot;. That would hopefully send it back out again and come back in. Having it come back in on a different forwarded port, would shunt it to a different webserver that would be listening on that different port.

I've never actually setup an automatic redirect before but obviously it's done all the time - maybe via some script or something.
 
Actually it's RC5 &amp; OGR ppstats that I have running on the Linux box 🙂

Ahh... then kill the friggin' IIS. 😛

I have the pproxy running on my 2K (I run both a port 80 and 2064 one) and have a share mounted between the pproxy's logs directory on the 2K and my linux box with ppstats, and the linux displays the stats via Apache like this. Not a problem. 🙂
 
Yes using a different port like 81 would allow me to route the traffic via the proxy. That might be a solution. I just have to include the port in the link to the non standard box.
 
I'll think I will use that solution 🙂

Thanks

PS: I can't drop the IIS server since I use it for ASP development.
 
Your redirect idea should work as long as your setup allows for loopback. You could just run each webserver on a differnt port.
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top