CODEWITHSUNDEEP
.htaccessmod-rewrite
Satchel
Satchel

Reputation: 16734

How do I do a .htaccess rewrite that masks the forwarded URL?

I have a url that is www.blahblah.com/something

That is a remote service, I don't have anything to do with it.

How can I use .htaccess on my own server and rewrite from www.myurl.com so that the content displayed is all www.blahblah.com/something, but the address bar still reads www.myurl.com

Upvotes: 2

Views: 11453

Answers (3)

Dani
Dani

Reputation: 11

Try this:

RewriteCond %{HTTP_HOST} ^DomainA.com
RewriteRule ^(.*) http://DomainB.com/$1 [P]

It works for me.

Source: http://www.inmotionhosting.com/support/website/htaccess/redirect-without-changing-url

Upvotes: 1

Dirk Leuther
Dirk Leuther

Reputation: 103

mod_rewrite is the right way.

  1. Make sure it is mod_rewrite is activated in our apache conifiguration.

  2. add to the .htaccess

    RewriteEngine On
    RewriteBase /
    RewriteCond %{HTTP_HOST} ^www\.blahblah\.com$ [NC]
    RewriteRule ^(.*)$ http://www.myurl.com/$1 [R=301,L]

RewriteCond defines the condition. In this case if the http_Host is www.blahblah.com
RewriteRule defines what to do. In this case forward to your target domain. $1 is the rest of your URL

More Details you can find here: http://httpd.apache.org/docs/current/mod/mod_rewrite.html

Upvotes: 0

cegfault
cegfault

Reputation: 6632

No, this is not possible with foreign urls.

You can, however, do this locally. For example, look at this htaccess file:

RewriteEngine On
Options +FollowSymlinks
RewriteBase /
RewriteRule ^some/test/url$ index.php?some=test&or=url [L]

In this scenario, if you visit www.myurl.com/some/test/url it will show as such on the browser, but your server will actually be running index.php in your document root with the parameters some=test&or=url.

This is only possible for scripts running on your server. You cannot do this on another server/domain. If you try this (eg, by changing index.php?some=test&or=url in the example above to http://www.blahblah.com/something), then apache will just redirect the browser to that url.

htaccess (Apache) makes the connection to the user, and the user is expecting a response from YOUR server. If you try to load content from another server, Apache would have to make that connection, load the resulting HTML or whatever, and pass it back to you. But this gets messy, especially when you get into cookies, SSL, javascript, etc.

My question is: why do you actually need this? I'm not sure I understand why it is a problem if the user's url changes. If it's a service you have no control over, why is it so bad to just send them to it?

You might want to research more about cache servers, or using PHP to to make the http call to the server you want and "pass through" the content, assuming you know beyond a doubt there will be no issues with cookies or SSL or whatever. But again, why not just send them to the proper URL?

Upvotes: 2

Related Questions