No URL inspection, just basic destination nat, when you access services online you only refer to the URL while you are making DNS look-up, after DNS return the IP address to you, you start using that IP address to access the same resource online.

DOCs:

Cisco ASA configuration guides:

http://www.cisco.com/en/US/products/ps6120/products_installation_and_configuration_guides_list.html

I think demikid is referring to the URL contained in the HTTP GET request. While it's true that when you type a URL into your browser it is translated to an IP address so that the server can be located, the original URL is still sent at Layer 7 in the HTTP request message.

Unfortunately I don't think an ASA has the capability to route based on the HTTP host header. I generally use Microsoft ISA server (now called Forefront TMG) to accomplish this.

That being said, you can have a single web server host multiple sites and have the web server do the redirecting for you. For example, if someone visits your site at www.somesite.com, the ASA would direct this to the (only) web server. The web server would then check the value of the HTTP request and send back the appropriate site. Then if someone accesses www.anothersite.com, the same web server would send back a different site based on that URL. The ASA simply sends all HTTP requests to the same server and lets the server figure out which site was requested.

This can be done in both IIS and apache. I can't remember how to set it up in apache, but in IIS you simply edit the host bindings to include the URL. I've attached a screenshot showing where this is done in IIS 7.

Of course, if you have multiple sites on multiple servers, this won't work for you. You either have to consolidate them to a single server, or come up with a different solution.

Hope that helps, Josh

In Apache it is called virtual host, and that is exactly what I referred to, you redirect traffic to single server and the server figure out what service is requested.

if you need multiple services with single domain, on multiple servers behind ASA, I think there is a method to accomplish that, but I am not sure what its name, I will further check, if I find anything I will post it here to you again.

If you want to separate service based on port number, it is very easy, as the access list which the nat depends on, will specify the port.

Cheers,

Could you please give a graphical demonstration, and some detailed descriptions, so we understand exactly your scenario.

Thanks