I think you could probably rig it up with URL filters and application policies to achieve the same thing ISA does today. But for a basic web server I can't imagine you would need more than a basic NAT policy terminating on the untrust side and a basic security policy to allow web-browsing / ssl to your web server.
I am wondering the same thing. If you come across any articles on configurating PA as a reverse proxy please post them to this thread. I have not seen a config option that would allow inbound URL's to be passed to internal destinations based on the inbound URL request.
Internet request to www.website1.com --> Palo Alto --> Web Server 1 - 10.0.0.1
Internet request to www.website2.com --> Palo Alto --> Web Server 2 - 10.0.0.2
Internet request to www.website3.com --> Palo Alto --> Web Server 3 - 10.0.0.3
ISA not only does a reverse proxy but much more. The "publishing" concept is more complex than a simple NAT. ISA interacts in authentication process, single sing-on, kerberos delegation, AD integration, publishing certificates, etc.
PAN is a firewall ISA is a firewall + publisher for MS infrasctructure.
Click Accept as Solution to acknowledge that the answer to your question has been provided.
The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!
These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!
The LIVEcommunity thanks you for your participation!