tag:blogger.com,1999:blog-13087824.post828501715747636058..comments2022-11-28T09:19:50.031+01:00Comments on Just notes: ASP.NET and subdomains - reloadedMaciekhttp://www.blogger.com/profile/15440998339849780775noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-13087824.post-73923341821782597502009-10-05T12:17:11.160+02:002009-10-05T12:17:11.160+02:00Nice post. Thanx for sharing this valuable informa...Nice post. Thanx for sharing this valuable information. Please provide more information over it. Provide links to related topics if possible.nintendo ds r4http://www.r4-ds-card.comnoreply@blogger.comtag:blogger.com,1999:blog-13087824.post-92038578595160075452008-09-24T17:50:00.000+02:002008-09-24T17:50:00.000+02:00Hi Maciej !!!Thanks for your help! Your answer was...Hi Maciej !!!<BR/>Thanks for your help! Your answer was very helpful for me. So, I'd like to ask you some other little things (sorry, i am abusing your generosity :D).<BR/>The first one is related with the way you manage each request from different subdomains. I understand how DNS wildcards works. So, I understand you must parse the url from request, and then check, for example, if the subdomain-user you get is already registered in the database of the application. If so, you can figure out which page to render, right?<BR/>Well, the idea is the user can reach all its stuff through userxx.myapp.com/profile instead myapp.com/users/profile.aspx?userid=8. Does it make sense for you? The goal is keeping a clean url. How do you manage this issue? <BR/>Do you dynamically create each subdomain in your hosting server? <BR/>Or do you use url rewriting for this? Do you have any code sample code for testing that?<BR/>Sorry for my annoying questions :(.<BR/>I hope you can help me with this. <BR/>Many, many thanks in advance!Anonymousnoreply@blogger.com