StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

PO
primarykey
Id
14299423
data
AcceptedAnswerId
0
AnswerCount
0
ClosedDate
CommentCount
0
CommunityOwnedDate
CreationDate
2013-01-13T00:28:52.013
FavoriteCount
0
LastActivityDate
2013-01-25T01:15:46.233
LastEditDate
2013-01-25T01:15:46.233
LastEditorUserId
1107593
OwnerUserId
1107593
ParentId
13979802
PostTypeId
2
Score
0
ViewCount
0
LastEditorDisplayName
text
Body
I think you're confusing Redirecting and Rewriting here - the behaviour you describe is exactly what I would expect given the rules cited. Initially the request is being redirected to www.misite.com/subdomain and then by virtue of your first rule that request is being redirected again to www.misite.com/main/subdomain. I think what you want to be doing here is rewrite the requests to serve the correct content for each sub-domain. Redirection effectively means "if a request for URL 'A' arrives, forward the browser on to URL 'B'". Rewriting the request effectively means "if a request for URL 'A' is received then serve resource 'B' as if it were at URL 'A'". I'm assuming you have the following structure- -wwwroot --main --subdomain Presumably what you want happen is that when a user goes to www.domain.com/default.aspx, the default.aspx document in the "main" directory is served, and likewise when the user visits subdomain.domain.com the default.aspx document in the "subdomain" directory is returned. I'm also assuming you don't want the folders themselves to be part of the path, i.e. not subdomain.domain.com/subdomain/default.aspx <pre><code><rule name="Rewrite to Main directory" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAll"> <add input="{HTTP_HOST}" pattern="^www.misite.com(/.*)?$" /> <add input="{PATH_INFO}" negate="true" pattern="/main/" /> </conditions> <action type="Rewrite" url="/main/{R:1}" /> </rule> <rule name="Redirect to WWW" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAll"> <add input="{HTTP_HOST}" pattern="^misite.com(/.*)?$" /> </conditions> <action type="Redirect" url="http://www.misite.com/{R:0}" redirectType="Permanent" /> </rule> </code></pre> I've left the second part of your first code block as a redirect as it is generally considered bad practice to have identical content available at multiple URLs for SEO (see <a href="http://support.google.com/webmasters/bin/answer.py?hl=en&answer=66359" rel="nofollow">http://support.google.com/webmasters/bin/answer.py?hl=en&answer=66359</a>) and will cause you problems with analytics. In this case I have chosen to redirect domain.com/default.aspx to www.domain.com/default.aspx, but it would be equally valid to choose to do it the other way around - you just need to make a choice and apply that consistently within your site. I have dropped the /main/ part of the redirection path/URL as the content in the /main/ directory is what should be served by the request anyway, leaving that in the path would effectively be looking for /main/main/default.aspx. I have also added a negate on the path info condition on the first (rewrite) rule, meaning that if a request that did arrive for www.domain.com/main/default.aspx it would not be rewritten to serve content from the sub-directory - /main/default.aspx would be served instead of the (presumably non-existent) file at /main/main/default.aspx. Lastly the sub-domain is also changed to a rewrite. <pre><code><rule name="Rewrite for Subdomain" stopProcessing="true"> <match url="(.*)" /> <conditions logicalGrouping="MatchAll"> <add input="{HTTP_HOST}" pattern="^subdomain.misite.com(/.*)?$" /> <add input="{PATH_INFO}" negate="true" pattern="/subdomain/" /> </conditions> <action type="Rewrite" url="/subdomain/{R:1}" /> </rule> </code></pre> See <a href="http://weblogs.asp.net/owscott/archive/2010/01/26/iis-url-rewrite-hosting-multiple-domains-under-one-site.aspx" rel="nofollow">http://weblogs.asp.net/owscott/archive/2010/01/26/iis-url-rewrite-hosting-multiple-domains-under-one-site.aspx</a> for more info on this topic.
Tags
Title
singulars
PostAcceptedAnswerId
1. This table or related slice is empty.
PostParentId
1. POHow to create custom rules in IIS Rewrite module for my sites
 singulars
 PostTypePostTypeId
 PTQuestion
PostTypePostTypeId
1. PTAnswer
UserLastEditorUserId
1. USpwdst
UserOwnerUserId
1. USpwdst
plurals
PostLinksPostIdRelatedPostId
1. This table or related slice is empty.
PostLinksRelatedPostIdPostId
1. This table or related slice is empty.
PostsAcceptedAnswerId
1. This table or related slice is empty.
PostsParentIdCreationDate
1. This table or related slice is empty.
VotesPostIdCreationDate
1. This table or related slice is empty.
CommentsPostId
1. This table or related slice is empty.

Querying!

Guidance

A row detail

Detail views are divided into sections. All the information in the data section comes from columns in the selected row. The other sections display data from other, related rows.

Related data can be related in a to-one or a to-many fashion. Captions of data related in a to-many fashion link to a list view showing a filtered view of the table.

Try moving around until you find a non-empty to-many entry and click on the label to get to one. You can move back to the root by clicking on the database name in the header.