-
www. vs non-www.
I created a virtual directory and pointed the site/URL to the directory that the page should be running at. If I go to browser and type http://www.mytestwebsite.com/about.html it works, but if I type http://mytestwebsite.com/about.html, it says page cannot be displayed.
So it seems to me it's the matter of whether I put in www. or not.
Is there a way I can fix this using virtual directory/anything that may help?
-
Re: www. vs non-www.
Not sure if this would help or not?
-
Re: www. vs non-www.
https://httpd.apache.org/docs/2.2/vh...ame-based.html
If you have ServerName inside the <VirtualHost> directive set to www.example.com then you would set ServerAlias to just example.com, so it looks for both the www and the non-www domain names when deciding which virtual host to send the request to.
For IIS, you would set the appropriate Host Headers on the Site in IIS Manager to check for www.example.com and also example.com on port 80 (and 443 if using ssl).