URL Forward/Redirect RRS feed

  • Question

  • User389791195 posted


    I am transitioning off of a TMG 2010 implementation, where I have several websites published on one public IP using the a TMG web listener and host headers, but going to several local IPs.

    The new environment has a Barracuda X200 that can't handle host headers or a web listener, like TMG did.  All port 80 traffic will go to the same public IP and forwarded to one local IP on port 80.

    I'd like to have an IIS install behind the X200 that will be forwarded the port 80 traffic, then based on host header info, forward that onto various other local IPs.

    After spending quite a few hours researching and testing, I'm finding that combinations of URL redirecting, URL rewriting, and using ARR just aren't fitting my scenario.

    Simply put, here's the steps I'd like:

    1) browser requests website1.public.com, resolves to public IP
    2) on the X200 forwards the traffic to a local IP,
    3) IIS listening on hears the traffic looking for website1.public.com, and then forwards it to a different local IP,
    4) IIS on the next local server, responds to website1.public.com

    This scenario is stupidly easy to publish using TMG 2010, but doesn't seem possible using just IIS.

    Any help would be greatly appreciated


    Thursday, July 27, 2017 8:46 AM

All replies