Guest User!

You are not Sophos Staff.

Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 4 replies
  • Answers 1 answer
  • Subscribers 27 subscribers
  • Views 8197 views
  • Users 0 members are here
Options
Suggested
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

web server using paths

BenUecker

I have 2 web servers.  One on one IP (web server 1) and another server on another IP (web server 2).  Web server 1 has been working great as setup in the security policies.  When adding web server 2 I assume I need to enable path specific routing as these are two completely different sites on different servers.

The paths setup are the default one for server 1.  / and then the web server name

The 2nd path I setup as /iqanywhere which is the folder name that the 2nd website resides in.  I've also added the domain and the static ip in the domain section.

It seems that whatever I pick it doesn't look at the /iqanywhere path and simply defaults to web server 1.  Am I missing a step?



This thread was automatically locked due to age.
Parents
  • 0

    Hi,

    I'm not completely sure what you're trying to do but I just explain how it works in general. ;-)

    You have

     * web server 1 with internal FQDN / IP address, e.g. internal1.local (HTTP port 80)
     * web server 2 with internal FQDN / IP address, e.g. internal2.local (HTTP port 8080)


     * registered external domain name(s),  e.g. externalA.com

    Basic Setup


    You create a Firewall rule (HTTP based Business Application Rule)

     * domain name: externalA.com
     * hosted address: the IP address where externalA.com resolves to
     * web Servers: web server 1 and web server 2
     * HTTP, port 80


    What happens:
    If you request http://externalA.com/ it forwards the request alternately to web server 1 (to http://internal1.local/) and web server 2 (to http://internal2.local:8080/)
    If you request http://externalA.com/mypath/ it forwards the request alternately to web server 1 (to http://  internal1.local/mypath/) and web server 2 (to http:// internal2.local:8080/mypath/)


    Advanced Setup with path-specific routing

    You enable path specific routing

     * path '/': only web server 1
     * path '/mypath/': only web server 2

    What happens:
    If you request http://externalA.com/ it forwards the request only to web server 1 (to http://internal1.local/)
    If you request http://externalA.com/mypath/ it forwards the request only to web server 2 (to http:// internal2.local:8080/mypath/)

    I hope that makes it more clear.

    Best,
     Sabine

    Edited because the stupid forum software break my example links. Remove the whitespaces in the links where necessary. ;-)

Reply
  • 0

    Hi,

    I'm not completely sure what you're trying to do but I just explain how it works in general. ;-)

    You have

     * web server 1 with internal FQDN / IP address, e.g. internal1.local (HTTP port 80)
     * web server 2 with internal FQDN / IP address, e.g. internal2.local (HTTP port 8080)


     * registered external domain name(s),  e.g. externalA.com

    Basic Setup


    You create a Firewall rule (HTTP based Business Application Rule)

     * domain name: externalA.com
     * hosted address: the IP address where externalA.com resolves to
     * web Servers: web server 1 and web server 2
     * HTTP, port 80


    What happens:
    If you request http://externalA.com/ it forwards the request alternately to web server 1 (to http://internal1.local/) and web server 2 (to http://internal2.local:8080/)
    If you request http://externalA.com/mypath/ it forwards the request alternately to web server 1 (to http://  internal1.local/mypath/) and web server 2 (to http:// internal2.local:8080/mypath/)


    Advanced Setup with path-specific routing

    You enable path specific routing

     * path '/': only web server 1
     * path '/mypath/': only web server 2

    What happens:
    If you request http://externalA.com/ it forwards the request only to web server 1 (to http://internal1.local/)
    If you request http://externalA.com/mypath/ it forwards the request only to web server 2 (to http:// internal2.local:8080/mypath/)

    I hope that makes it more clear.

    Best,
     Sabine

    Edited because the stupid forum software break my example links. Remove the whitespaces in the links where necessary. ;-)

Children