This discussion has been locked.

You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Host Header Routing

So just a quick question and not even sure if it is possible but I want to setup a secondary webserver on my network. This webserver will host a different site than what my current server is hosting. Both servers will be listening on port 80. Is it possible with Astaro to configure a rule that checks the host header? So that way if a request for the new server comes in it routes it where it needs to go?

This thread was automatically locked due to age.

Parents

0 BAlfson over 15 years ago

Lemo, what you want to accomplish is being done by many V8 users. What do you see in the 'Web Application Firewall' log? Maybe you could show us edits of the virtual server definitions for two domains that should resolve to two different servers.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Reply

0 BAlfson over 15 years ago

Lemo, what you want to accomplish is being done by many V8 users. What do you see in the 'Web Application Firewall' log? Maybe you could show us edits of the virtual server definitions for two domains that should resolve to two different servers.

Cheers - Bob
Cancel
Vote Up 0 Vote Down

Cancel

Children

0 jshockley over 15 years ago in reply to BAlfson

Just tried to setup some of my host headers via Web Application Firewall. Setup was:

Virtual Web Server settings:
Type: Plain (HTTP)
Domain: domain.com and www.domain.com
Interface: External (one of my ISP IP's)
Port: 80
Real Web Server: Server2008-01 and Server2008-02
Firewall Profile: Advanced Protection (Standard included profile)
Enable HTML rewriting: unchecked

Real Server settings:
Host: Defined to internal host IP
Type: Plain (HTTP)
Port: 80
These real servers are 2008 R2 IIS 7.5 boxes with websites routing by host headers.

When I went to www.domain.com from external machine, I got the website that is *:80 and not www.domain.com:80 website.

Any ideas?

Jared
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 15 years ago in reply to jshockley

Got any screenshots, that will help.
Cancel
Vote Up 0 Vote Down

Cancel
0 jshockley over 15 years ago in reply to BrucekConvergent

What kind of screenshots do you want?? [;)]

Just kidding. Here's the virtual server's settings:
virtualweb.JPG

Here's the real server's settings:
realweb.JPG

Here's the firewall profile:
fwprofile.JPG

Thanks again and thanks a ton Bruce for the other help!

Jared
- virtualweb.JPG
- View
- Hide
Cancel
Vote Up 0 Vote Down

Cancel
0 BrucekConvergent over 15 years ago in reply to jshockley

Try defining the websites separately --- I think the Astaro is normalizing the host header info.
Cancel
Vote Up 0 Vote Down

Cancel
0 jshockley over 15 years ago in reply to BrucekConvergent

I just checked that and still had the same result ... getting the *:80. I am seeing this in my Web Application Firewall log for the request at that time.

2010:08:19-14:05:00 asg reverseproxy: [Thu Aug 19 14:05:00 2010] [error] [client 174.121.74.234] Hostname in HTTP request does not match the server name

So I need to make Virtual Servers for each host header?

By the way, sorry to hijack this thread ...
Cancel
Vote Up 0 Vote Down

Cancel