Bekijk de volledige versie : Host Header
When defining a web site in IIS, there is an option called host header, which does nothing more than to distinguish between different URL's pointing to the same IP address.
What I want to accomplish is the following:
One URL (i.e. www.numberone.com) must be redirected to a client in my LAN, another URL must be "redirected" to the router (running webserver on it too).
Is this possible?
How about you catch all different URLs to the same site, and then throw them to different IPs based on which one was called?
As done here (in this case, asp): http://www.4guysfromrolla.com/webtech/code/multihost.asp.html
How about you catch all different URLs to the same site, and then throw them to different IPs based on which one was called?
As done here (in this case, asp): http://www.4guysfromrolla.com/webtech/code/multihost.asp.html
Because I do not have (and do not want) PHP, MySQL and Apache on the Webserver (it runs IIS6).
Because I do not have (and do not want) PHP, MySQL and Apache on the Webserver (it runs IIS6).
Then I don't get your problem. You don't need any of those, just a single ASP page (which IIS supports natively) catching Request.ServerVariables("SERVER_NAME") and sending off request where they belong based on that info.
Then I don't get your problem
That is because I put it in a really awful way, sorry for that.
Now, my website (ASP/ODBC) runs on a windows webserver on my LAN, traffic is forwarded on the WL500gx. I want a second website (running PHP) on the WL500gx, so I need to distinguish between the two websites by host header. (the first being macloud.kicks-ass.net and the other being jbr.homeftp.net). Can I accomplish this by routing traffic for both sites to the appropriate destinations?
I see the problem. One solution, not the best one I suppose, is to have the router forward everything to your windows server, then use server variables to determine which of those addresses was called. Then use server.execute to run php stuff on your router through your LAN.
I think the reason I think like this is that I program on IIS on a daily basis. The php people might well give you a better solution to do this on the router, and forward only what needs to be forwarded...