I have a website on the IIS as the default website. It is in "c:\interpub\wwwroot". When I request "www.mysite1.com", I get to this site.
Now I want to add a second website on the same IIS server. I want to store it in "c:\mysecondsite". When I request "www.mysite2.com", I wish to get to this second site.
NOTE: I don't want the second site to become an application inside the first site. In other words, I don't want to access the second site using "www.mysite1.com/mysite2".
How do I do it?
Related
I have a Windows Server 2012, with IIS 8 installed. I have multiple websites there. I also have the Default Website.
When I create a new website like www.abc.com and abc.com, it works fine. However, when a customer enters an invalid subdomain to abc.com (a subdomain definition that is not actually there), like xyz.abc.com, it automatically redirects to my Default Website which is a landing page.
Instead, I want to return a custom 404 page from IIS. Is that possible?
Thanks.
Your DNS should be taking care of that. If xyz.abc.com doesn't exist in the zone, no browser should be coming even close to IIS.
That is, unless you have a wildcard record configured. It sounds like you might.
Give it a look.
We have an IIS web farm, of which consisting an load balancer, 4 ARRs, and 2 ASP.NET application servers running DNN CMS. The 4 ARRs will URL rewrite to DNN application servers. We have more than 100 URLs that need to be redirected into more specific resources within the website.
For example, when a user types in http://www.abcd.com/product1 from outside, the desired outcome is to redirect to www.abcd.com/index.aspx?articleid=1234 , we have configured such behavior within DNN environment, and we can sure that it works, as when we browse the site within the DNN application server, the DNN is able to detect the URL and perform redirection accordingly.
Problem occurs when we attempt to browse the http://www.abcd.com/product1 from LB and ARRs, when we type http://www.abcd.com/product1, it simply go back to http://www.abcd.com mainpage, which the redirection doesn't work at all. No IIS level HTTP redirection has been performed at the ARRs and LBs, the only setting is the default URL rewrite rule which will rewrite the URL to backend DNN servers.
Same question has been posted in IIS forum as well, it is just that I decided to post it here again to gain more exposure.
When going through the ARR are you calling off to the specific IP? For example does http://www.abcd.com/product1 become http://xxx.xxx.xxx.xxx/product1 by chance?
If so, you might want to add those as additional portal aliases to the DNN site.
Otherwise, you will might want to use something like Fiddler to see exactly what is going on with redirects/responses.
This is not SEO related in any way please do not post any thing about SEO ranking as it is not a factor here.
I have 2 urls
old.websitename.com and new.websitename.com
I need to support both urls for a certain length of time and rather than creating 2 sites in IIS I wanted to see if there was a way of doing this by hosting just a single site.
I can not do any redirects on the urls and both urls will need to be active eg I can not have a user go to old.websitename.com and be redirected new.websitename.com. if they go to old.websitename.com they need to stay on that url and not be redirected in any way.
Can this be done on IIS 7 (note this is IIS not Apache or PHP based)
You just need to create a binding for each hostname.
Right click the site. "Edit Bindings"
Click Add
Enter the hostname
Repeat 1-3 for each hostname.
I have an application that is currently deployed (ex. www.example.com ). However, now we have a "secure" subdomain, which will take all of the requests that need to be encrypted (ex. secure.example.com). The site that is at www.example.com is currently mapped to C:\inetpub\example.com\wwwroot\, and I've mapped secure.example.com to C:\inetpub\example.com\wwwroot\secure.
However, since secure.example.com was setup as a new website within the IIS Manager, when the secure site is visited, it displays an error since there is no web.config associated with this website; however, this is the way I want it since I want this to be a part of the application that is in the parent directory.
I think what you really meant to do was just right click on the web site for example.com and edit the bindings. In there you can add host names to that site.
Make sure you add them for port 443 which is SSL.
Map both the IIS virtual directories/web sites to the same directory, and check that are both using the same IIS application name.
(Not tried this, but can't recall seeing anything to say it would not work.)
I have a Windows 2008 Server with IIS7 on it and a web page running under the name, let's say myApplication. I have a domain name that points to the IP of my server, let's say myApplication.com.
In order to access my application I have to enter http://myApplication.com/myApplication.
If I write http://myApplication.com/ I arrive to the IIS7 start page. Is there a way (besides rewriting the iisstart.htm to make a JavaScript or meta-data redirect) to automatically open the myApplication when someone enters "http://myApplication.com/"?
What I would like is the following:
The user enters in the browser: "http://myApplication.com/"
He/she is taken to "http://myApplication.com/myApplication"
In the URL bar of the browser only "http://myApplication.com/" shows and everything inside the application is relative to this URL.
Generally when I configure IIS, I set the properties for the "default web site" to a folder that doesn't contain anything, then create individual entries within IIS for each web site. For example, you would create a new entry for "MyApplication.com" and set its home directory to the proper folder on the server that contains your root files (usually c:\inetpub\wwwroot\myapplication.com\ but it could be anywhere you like).
It sounds as if you have created a folder for your application, but do not have a specific entry in IIS configured to handle the requests and load files from the proper folder.
If you have a dedicated IP address for the application, be sure to specify that IP within the site settings for that site. If you're using a single IP for multiple sites, configure the IP AND hostnames/domains that will be used to access that site so IIS will know which site entries belong to which domains and where to route the requests.