Mobile app version of vmapp.org
Login or Join
Steve110

: Forwarding domain and masking url I have website on wordpress with responsive theme. It is located on my server hosted by apache. Everything works well when I access site with IP address. The

@Steve110

Posted in: #DomainForwarding #Htaccess #Url

I have website on wordpress with responsive theme. It is located on my server hosted by apache. Everything works well when I access site with IP address. The problem is when i try forward my domain to this address.

I have two options on my domain control panel:

Forward domain.com on IP address 111.111.11.11:8080/website Result: When i type domain.com in browser i see domain.com url but site doesnt load corectly on smartphones

Forward 301 domain.com on IP address 111.111.11.11:8080/website Result: Type domain.com, sites loads corectly on mobiles but in url i see 111.111.11.11:8080/website but i want to see domain.com

I know that in the first case the problem is that domain forwarding adds iframe to site and that is why the responsive wiev doesn't load.

I want to use 301 forwarding and mask url with domain.com. How i can achieve on wordpress.

10.01% popularity Vote Up Vote Down


Login to follow query

More posts by @Steve110

1 Comments

Sorted by latest first Latest Oldest Best

 

@Berumen354

There are two possibilities that I am taking from your question so I will cover them both.

Make 111.111.111.111:8080/website Appear as www.domain.com:8080/website In this instance all you need to do is setup a standard DNS record pointing domain.com to your server's IP address. The important thing to note here is that DNS just translates a domain name to an IP address, the port number and file path must be in the address bar as well.

Make 111.111.111.111:8080/website Appear as www.domain.com In order to make this work you need to setup a proxy server. A proxy server works by translating the URL you are requesting into something else. Commonly used to provide external access into internal company sites (such as allowing you to access intranet.local externally of the local network with the address intranet.domain.com). This would allow you to hide the IP address, port number, and even the site specific path (so that domain.com/about/something.html would allow access to 111.111.111.111:8080/website/about/something.html through the proxy). The difficulty here is securing the proxy environment. A poorly secured proxy server can be a huge security hole into your local network, and can also be used as a launching point to attack or spam other websites and appear as though to be coming from your network. This can get extremely complicated to do and is not for someone without experience in network security and at least an awareness of network protocols. The vastly better solution if possible would be to change the port that serves the HTTP requests from 8080 to port 80 which is the standard HTTP port and so can be ommitted from a HTTP request as no specified port in HTTP is taken to mean port 80.

10% popularity Vote Up Vote Down


Back to top | Use Dark Theme