<p>I have a php server that is running my domain name.  For testing purposes I am running an asp.net on a dotted quad IP. I am hoping to link them together via either PHP or some kind of DNS/<code>.htaccess</code> voodoo.</p>

<p>So if I go to <code>www.mydomain.com/test</code> it redirects (but keeps the url  of (<code>www.mydomain.com/test</code>) in the browser's address bar and the pages are served by the dotted quad IP asp.net box.</p>

[{'answer_id': 46117, 'author': 'Lee', 'author_id': 3556, 'author_profile': 'https://Stackoverflow.com/users/3556', 'pm_score': 0, 'selected': False, 'text': "<p>It is quite possible, if I understand what you're getting at.</p>\n\n<p>You have a PHP server with your domain pointing to it. You also have a separate ASP.NET server that only has an IP address associated with it, no domain.</p>\n\n<p>Is there any drawback to simply pointing your domain name to your ASP.NEt box?</p>\n"}, {'answer_id': 46143, 'author': 'Will Harris', 'author_id': 4702, 'author_profile': 'https://Stackoverflow.com/users/4702', 'pm_score': 4, 'selected': True, 'text': "<p>Instead of pointing <code>www.yourdomain.com/test</code> at your test server, why not use <code>test.yourdomain.com</code>?</p>\n\n<p>Assuming you have access to the DNS records for <code>yourdomain.com</code>, you should just need to create an A record mapping <code>test.yourdomain.com</code> to your test server's IP address.</p>\n"}, {'answer_id': 46162, 'author': 'mweerden', 'author_id': 4285, 'author_profile': 'https://Stackoverflow.com/users/4285', 'pm_score': 0, 'selected': False, 'text': '<p>The easiest way is to make <code>www.mydomain.com/test</code> serve a HTML file which has a single frame with the plain IP address. However, this means that the URL in the (awesome) address bar always stays exactly the same, even if you click a link on the displayed page. (You can avoid this by adding <code>target=_top</code> in the <code>href</code>, but this would require some modifications to your "asp.net".)</p>\n\n<p>The only other way I can think of is to make <code>www.mydomain.com</code> act as proxy. That is, at <code>/test</code> it has a script or something that gets the page from your "asp.net" and forwards it to the client.</p>\n'}, {'answer_id': 46316, 'author': 'ceejayoz', 'author_id': 1902010, 'author_profile': 'https://Stackoverflow.com/users/1902010', 'pm_score': 0, 'selected': False, 'text': "<p>You can do this with a proxy, but I think Will Harris's answer is the best - use a subdomain.  Much simpler, and it'll get rid of issues with relative links as well.</p>\n"}, {'answer_id': 46368, 'author': 'John', 'author_id': 2168, 'author_profile': 'https://Stackoverflow.com/users/2168', 'pm_score': 0, 'selected': False, 'text': "<p>I agree that the sub-domain idea is the best, but if for some reason it doesn't work for you you could also have the php page at /test proxy requests to a URL at the dotted quad machine (using fopen to access the dotted quad URL).</p>\n"}]
['https://Stackoverflow.com/questions/46074', 'https://Stackoverflow.com', 'https://Stackoverflow.com/users/3135/']