In IIS7 using UrlRewrite module I want to do something likes this. I tried everywhere, possibly this is wellknown problem, but couldn't find any usefull solution.Url "http://tom.mydomain.com" should be read internally as "http://mydomain.com/dashboard?g=tom"I am using ASP.NET MVC, just in case info is required.
I just finished converting a static .htm site to a .aspx/master page site for a client. They have a number of google site links (that I've blocked) that are .htm, but they're still showing up on Google. To preserve old bookmarks (and google sitelinks), I'd like to rewrite the URL from http://www.site.com/about.htm to http://www.site.com/about.aspx.
I'm using urlrewriter already, I just don't know enough about it to know how to rewrite this url. Should be pretty easy, something like:
I've got a problem using outputcache together with urlrewriting. We've got an application that rewrites url (IE [URL]). Based on the URL (/about/) we figure out which content to show. Now we're trying to add outputcache to that page:
However, when we publish the page i'd like to invalidate the cache so that the editors see the change directly. But no matter what I try, I cannot seem to invalidate the cache. If I'd like to invalidate "/about/" I would like to do this: HttpResponse.RemoveOutputCacheItem("/about/"); That doesn't work unfortunately. The only thing that seems to work is: HttpResponse.RemoveOutputCacheItem("/page.aspx");
This clears the cache for all my pages, not just "/about/". Is there any way to invalidate the cache based on the url? Or should we provide a cache key or something per page to be able to invalidate the cache programmatically?
I am working on rewriting URLs Urlrewriting.net, and have run into what seems to be a common problem but I can seem to fix it. I'll present a simplified case.
The URL rewriting is working perfectly with the rule:
I now see the correct URL on the form action, and when debugging I can see the page load event firing.
The problem now is that every time the page loads Page.IsPostback is false, causing the page to rebind the DataList and therefore ignore the ItemCommand the buttons should be triggering.
if (!Page.IsPostBack) PopulateControls();
I'm using .NET 3.5 SP1, there is a ScriptManager on the master page but no UpdatePanel on this page. I've also tried resetting the Form.Action property and bypassing ScottGu's solution with the same result. If I go to the page URL directly without using the rewriter everything works fine.
I have a fully dynamic application that uses UrlRewriting.Net that works perfectly within the visual studio environment. As you can see from the rules within the web.config file below, UrlRewriting.Net rewrites the destination as "~/index.aspx?URLPath=$1&URLString=$2", basically index.aspx searches the database for the page properties and builds the page based on the parameters passed. There are no physical files for the website, only index.aspx with all pages and its webparts build dynamically on the fly. The application is compiled as ASP.NET 3.5 and runs on a Windows Server 2003 x64 standard edition.
To my knowledge the configuration you see in the web.config below should work in iis6, however does not . Does the installment of UrlRewriting.Net require configuration in iis6 as well?
I'm trying to implement custom urlrewriting in the global.asax of my website and i'm experiencing some troubles with updatepanels from the ajaxcontroltoolkit:second post back of my updatepanels seems to request the wrong url (ie : if my rewrited
url is /en-US/parentPage/myPage.html and the physical url is /default.asp?ln=en-US&page=myPage, the second post back request /en-US/parentPage/default.asp?ln=en-US&page=myPage, which leads to file not found ...)
I dont know if it matter but i desactivated the viewstate on the page by setting Page.EnabledViewState to false.To implement urlrewriting i used Server.Transfert(physicalUrl, true)
I'm using urlrewriting.net and want to add a rule to map all classic asp requests to default.aspx.Unfortunately my attempt below just results in a redirect loop, so I must be doing something wrong.
I'd like to know if there's something wrong with it. I'm trying to link all the http get requests made to one folder to be redirected to the images folder. So for instance when I make a request like this
I've used the UrlRewriting.Net module for a couple years now without any problems in Windows XP and Windows 2003. I just recently upgraded my home PC to Windows 7 and started developing a new website.The plan was to use .html extensions and rewrite them to their .aspx counterparts using the UrlRewriting.Net module. Everything works flawlessly in VWD 2008, but when I try running it through IIS7 it is a different story.
When I try to access a page via the .html rewrite I can no longer access Page.User; it keeps returning null. If I hit the page using it's .aspx extension, Page.User is correctly populated. I should also mention that I have a LoginView controller in my Master Page and it suffers from the same symptoms: When accessing via .html extension it shows the AnonyousTemplate; When using .aspx extension it properly shows the LoggedInTemplate. I'm guessing the two are related.
[Note: I've also tried extensionless URLs and they exhibit the same problem]
The only way I've gotten it to work is to switch the application pool to Classic, which then requires me to add an ASP.Net ddl handler for the .html extension [otherwise it is handled by the StaticFileHandler and comes up as a 404 error]. However, I'd like my web app to run properly for people without having to fiddle around with IIS.So I am left with several questions:Does anyone have ideas as to why Page.User always equals null for .html => .aspx rewritten pages?
Why does it work in VWD 2008, but not IIS7?
What changed from IIS6 => IIS7 that could have caused this?
[Note: I just tried a .aspx => .aspx rewrite and it did not exhibit the problem. Not really what I want, but thought I should mention it.]
I have a working website with multi language support. Now this multilanguage support its based on three flags (one for spanish, another for english and another for french) and cookies. I stablish a cookie with the current culture. Then I have resource files for each language (default.aspx.resx, default.aspx.en.aspx, default.aspx.fr.resx ...)All working ok.Now I want to change the language system to subdomains. I want es.mydomain.com, en.mydomain.com and fr.mydomain.com, because search engines dont index very well with cookie language system.
I have created three A ZONES (es, en, fr) in the DNS hosting provider. This A ZONES points to the same IP that the WWW ZONE. Even though www.mydomain.com takes the user to the default.aspx of the website, but the other zones not.en.mydomain.com, fr.mydomain.com and es.mydomain.com returns a webpage with the text: BAD REQUEST (INVALID HOSTNAME)I think I have to make some other change in my code (perhaps global.asax).I have done this in PHP web server, but I dont know how to do in a ASP.NET server.I have searched solutions, but I have a lot of confusing information, principally about DNS, but I think that this part its OK
I find myself in a difficult situation. We're working on an ASP.NET MVC 2 application which is comprised of multiple sections. It is a design goal to have these sections span across several subdomains. Each subdomain will have its own controller.
The challenge is that our hosting provider's control panel allows two forms of redirection for subdomains, and neither of them seem to fit the bill. The choices are:
Redirecting to URL. Choice is given whether to redirect to an exact destination or a destination relative to the request URL. Redirecting to a specific folder in my hosting space.
I'll try to illustrate the intended behaviour. Assuming the default route is {controller}/{action}/{id}, I'd like the URL http://subdomain.welcome.com/a/b be handled by the MVC Application like http://welcome.com/subdomain/a/b.
The URL redirection could solve this problem, except for the fact that the user sees a URL change occur in the browser. We don't want the client to see the redirection occur.
Redirecting to our MVC apps root folder doesn't work at all. The app doesn't pick up the request and a 4xx error gets passed back by IIS.
edit:
In the interest of finding an answer, I'll simplify this a bit. The "redirect to URL" doesn't do what I want so that leaves redirecting to a folder.
If I'm redirecting a subdomain to the root folder of my MVC App and IIS wont pick up the requests, is this a limitation of IIS or my provider?
[FYI - Posted the same thing over at StackOverflow]I've used the UrlRewriting.Net module for a couple years now without any problems in Windows XP and Windows 2003. I just recently upgraded my home PC to Windows 7 and started developing a new website.The plan was to use .html extensions and rewrite them to their .aspx counterparts using the UrlRewriting.Net module. Everythingworks flawlessly in VWD 2008, but when I try running it through IIS7 it is a different story.
When I try to access a page via the .html rewrite I can no longer access Page.User; it keeps returning null. If I hit the page using it's .aspx extension, Page.User is correctly populated. I should also mention that I have a LoginView controller in my Master Page and it suffers from the same symptoms: When accessing via .html extension it shows the AnonyousTemplate; When using .aspx extension it properly shows the LoggedInTemplate. I'm guessing the two are related.[Note: I've also tried extensionless URLs and they exhibit the same problem]The only way I've gotten it to work is to switch the application pool to Classic, which then requires me to add an ASP.Net ddl handler for the .html extension [otherwise it is handled by the StaticFileHandler and comes up as a 404 error]. However, I'd like my web app to run properly for people without having to fiddle around with IIS.
So I am left with several questions:Does anyone have ideas as to why Page.User always equals null for .html => .aspx rewritten pages?Why does it work in VWD 2008, but not IIS7? What changed from IIS6 => IIS7 that could have caused this? Any other thoughts on workarounds?[Note: I just tried a .aspx => .aspx rewrite and it did not exhibit the problem. Not really what I want, but thought I should mention it.]
I have setup my website (ASP.NET 3.5) with AJAX, running with no problems at all.
When I test my website locally and on my main top level domain, there are no problems.
When I'm on a subdomain page, AJAX client side framework fails to load. I observed the problem deeply and found that whenever I'm on a subdomain page, WebResource.axd DOES load but ScriptResource.axd DOESN'T load (returns 404 Not Found error). I think I should modify some entries at web.config file, but I have no idea on what to do?
I am running into a unique problem (not easily googleable). This is what I am trying to do:Will be using subdomains: x.abc.com, y.abc.com, z.abc.com, etc.There will be single website hosted at abc.comBased on the subdomain passed (x,y,z,etc.), I need to switch databases and web.configs (appsettings, authentication, authorization info)For ex: If a user goes to x.abc.com, the site will select appropriate db & config settings and forward user to abc.com with db & settings cached/saved for the user session.Is it possible to have one hosted site and multiple subdomains that select appropriate config settings? Reason I need to do this is because credit card processor needs static url for requests and responses.
We have two subdomains for the same site, we would like that depending on the visited subdomain the initial page varies. But in IIS the default document setting is based on the web.config so...We know that we could use the http:/subdomain/page.aspx but its a requirement that we use only http:/subdomain in the links
Desired example: Click in link http:/subdomain1.web.com --> http:/subdomain1.web.com/page1.aspx (our_website/page1.aspx) Click in link http:/subdomain2.web.com --> http:/subdomain2.web.com/page2.aspx (our_website/page2.aspx)
I'm writing a SaaS app in C#/ASP.NET, hosted with IIS7. I want to create a personalized subdomain for every customer that signs up, i.e. fred.mydomain.com, bob.mydomain.com, each of which will point to the same app, just with a different skin per customer.
How do I create these subdomains programmatically?
I would like to create subdomains Dynamically under my domain using asp.net ,C#? I can not find good solution for this. What are the things i should do to complete this.
Scenario:
1.user register with site
2.domain name should be: http://username.domain.com
I want to deploy multiple asp.net applications on same hosting with subdomains. How it should be manged ?
I just created a subdomain and deploy application in its folder; when I tried to access application with subdomain it shows the following error:
An application error occurred on the server. The current custom error settings for this application prevent the details of the application error from being viewed remotely (for security reasons). It could, however, be viewed by browsers running on the local server machine.
Consider that I want to create 10 websites in IIS, each of them pointing to the same website on local hard drive, each one running the same code, but on different subdomain.subdomain1.domain.com, subdomain2.domain.com, ..., subdomain10.domain.comHow can I add multiple connection strings in my web.config file and bind each connection string to a different subdomain ?I want to do this because every website will have a different database with different data.