I have a situation that I think is a bit different from most. It's certainly different from any that I've encountered before:
I'm building a site for a client who wants/needs to retain full control over their canonical domain. Instead of simply pointing www.theirdomain.com
and theirdomain.com
to my server IP, they want to route traffic to them and let their Big-IP device send that traffic on to us at client.mydomain.com
. I don't know Big-IP, but I suspect/assume this is a rewrite and the user will only see theirdomain.com
.
In addition, the client has 2 subdomains whose landing pages will be served by my app and their IS team doesn't want anything to do with them. They're just updating DNS for those domains to point to my server. The landing pages, though, are served at client.mydomain.com/path/to/landing/page
.
Since we don't want end users to ever see the client.mydomain.com
, though, my normal process of doing a 301 redirect to the answering URL would seem to create some unnecessary traffic:
- My server answers the request to
sub.theirdomain.com
- Instead of simply answering the request, my server redirects to
www.theirdomain.com/path/to/landing/page
- Their Big-IP sends them right back to my server (the same one they just left), but with the correct domain.
- My server renders the content.
In step 2, instead of redirecting out to their device, can I simply rewrite the URL to www.theirdomain.com
and serve the content directly? Better ideas also welcome. As I said, this isn't something I've encountered before and I'm looking for options.
proxy pass
?