To Change URL without redirect by .htaccess file?

[adi_ind_coder]

I have a Domain registered in GoDaddy say xyz.com, (URL1)and another host website say xyz.abc.com (URL2)!
I want to redirect URL1 to page to URL2 using forward feature permanent 301 in Domain registrar portal.
Forward with masking is not working in Mobile phone’s browsers, whereas it is working in Desktop browsers. Normal forward (without masking) is working but I don’t want the URL to change to URL2

Please share exact .htaccess file code to copy and keep in hosting website folder that will restore the URL to URL1 and not show URL2 instead after being forwarded.

Further will there be any difference of such .htaccess files if host server is nginix and or Apache. If so need .htaccess code for both version

[Greenreader9]

So you want to just 301 the old domain to the new one? It would be better to just add the old domain here as a parked domain to the new one, but it you really want to use .htaccess, see below.

Add this .htaccess to the original website:

301 oldpage.html https://newsite.com/newpage.html

Also, Forwarding with masking is not a great idea, please see the topic below to learn more about that.

Forward with Masking = Support.Google.Com refused to connect

Getting the message “support.google.com refused to connect” with two domains and test pages I have setup here this week, getting error on various browsers or PCs. Have multiple domains going to pages on my main hosting service, using ‘301 - forwarding with masking’ and no issue. Have found that when I use ‘302 - forwarding’ the problem goes away, the domain names work immediately and I can get to the site page fine. But this means, people see the full URL link instead of the domain…

InfinityFree servers use both NGINX and Apache configurations, however, NGINX does not support .htaccess, which is why we also use Apache.

Hope this helped!

[Admin]

This is not possible with .htaccess rules.

Why not just add the domain the right way?

@adi_ind_coder

Further will there be any difference of such .htaccess files if host server is nginix and or Apache. If so need .htaccess code for both version

NGINX doesn’t support .htaccess. We use both so you can use .htaccess while having the performance benefits of NGINX.

[alexvf]

Using 301 redirects in .htaccess will always redirect URL1 to URL2 and show URL2 to the users.
There’s not a way to mask it using 301 redirects because the point of doing it is exactly the opposite.
A 301 redirect not only redirects users to another URL but also informs search engines that the new URL is the correct one and that they should forget the old URL.