I have a particularly "hacky" question/solution and looking for some honest feedback.
In an enterprise system there are a number of requests that are destined for www.sometargeturl.com. These need to be diverted to www.newdestination.com.
Edit: We're not in charge of www.sometargeturl.com so can't put in 301 re-directs using .htaccess or anything here.
Rather than change all the code on the enterprise systems, I was wondering if a firewall/packet sniffer solution would work?
All traffic is routed through a Windows proxy server before it goes out onto the internet.
One solution I can think of would be to install a firewall or packet sniffer on the proxy server. The firewall would be programmed to look for packets addressed to www.sometargeturl.com and forward them instead to www.newdestination.com.
It's important that the full HTTP request is forwarded, and that it doesn't reach its original destination.
All thoughts appreciated, this isn't a great solution by any means!
Duncan
I don't know if this fits in your plan, but on an apache webserver a .htaccess file could do this redirection also for you
place a .htaccess file with the following line in the webserver documentroot of www.sometargeturl.com
Redirect / http://www.newdestination.com/
to do something like this you should setup static nat on a host in the middle. Setup a static nat rule sending their ip address to the ip address of the server you'd like their traffic to go to - I'm assuming you have access to their firewall or something like that. Make sure the site you want the request going to is setup to answer requests for www.sometargeturl.com. How to setup static nat depends on what networking gear you're using.