Configuration :: 301 Redirect Non-WWW Domain In Web.Config Using UrlRewrite
Mar 2, 2011
I have one web application that manages 20-30 websites (one asp.net engine loading different templates based on httphost)Im redirecting non-www requests to its www equivalent in my web.config using UrlRewrite.
We are using BlogEngine.net for our company blog and we'd like to start using feedburner. Since we already have an considerable amount of subscribers to our feed, we want to maintain the same url. The url of our feed would be: ~/blog/syndication.axd. What I'd like to do, is to maintain the URL, but redirect requests to this url to the feedburner URL. So, I started to use the urlMappings section in the web.config for that:
There is a strange behaviour with my web app which resides on the deployment server. This problem does not appears on the production enviroment (using the VS build-in development web server)
I am using URLRewriter and forms authentication on my web app. URL rewriting is performed by an http module on AuthorizeRequest. Also, runAllManagedModulesForAllRequests is enabled.
When I am trying to access some specific pages (NOT ALL OF THEM) with a rewriten url, IIS 7 returns me an 404 error.
Here are some of the rewriting rules:
Can be accessed BOTH rewritten and original url: <rewrite url="^/home.aspx" to="/ASPX_FILES/home.aspx" processing="stop" /> <rewrite url="^/product/(.*).aspx" to="/ASPX_FILES/item_details.aspx?id=$1" processing="stop" />
I have what I think is a very common scenario but I've searched quite some time now and can't seem to find the answer! I have a standard web app that has a web.config in the root directory. I have some account management pages in a subdirectory called Accounts. Any timeouts at the root level work fine - the user is redirected to Default.aspx as indicated in my Forms authentication. My problem is when the users are in the Accounts (or any) subdirectory and they go off for coffee and the app times out. On the next click, they get an error saying "Accounts/Default.aspx" cannot be found. And Default.aspx is not there as it sits at the root level. It's trying to redirect them to the default login URL as defined in the web.config file but that doesn't work when the user is sitting in a subdirectory. I don't want to put a default page in this any every sub directory. I have tried putting a web.config file in the subdirectory but it throws the error about machine to application level/IIS.
I've got an Search Engine Optimisation problem where users are able to access my site by specifying any sub-domain. This is causing duplicate page issues with SEO.For example if a user mis-types 'www' then posts a link on a forum, google is crawling 'wwww.domain.com'. Furthermore, google is also crawling 'domain.com'.I need a way of forcing the site to always redirect to 'www.domain.com' regardless of how the user accesses the site.
I am trying to achieve a SSO implimentation across my websites so i am using the machine key attribute to do so.now the trouble starts here as the website the user logs in is on the .net 1.1 framework and the website it it navigating to is .net 4.0.I have share the same machine-key across both the application . It works fine in my testing environment but as i move to the deployment server ,it just dosent work !So what i could do is read this article on MSDN :
http://msdn.microsoft.com/en-us/library/eb0zx8fc.aspx this tells me to add a domin attribute like below <forms loginUrl="~Login.aspx" defaultUrl="Default.aspx" protection="All" timeout="80" name=".ASPXAuth" domain="asbc.com"/> but this thing just dosent work on the 1.1 application and throws an error Unrecognized attribute 'domain'.
Where do i get to mention the domin in my 1.1 application.?
i have 2 domain names namely www.test.com and www.testltd.com. Now i would like to redirect www.testltd.com to www.test.comwhats the best way to do this. and what impact it will have in search engines. I mean google is indexing both of them.
This is not a duplicate post. I've looked through similar questions on SO but didn't find the solution to my problem.As someone has already suggested I should do the following to redirect www-url to non-www url (or vice versa):Here's the IIS7 rule to remove the WWW prefix from all incoming URLs. Cut and paste this XML fragment into your web.config file under
when users request http://test1.com/downloads, i need to redirect users to another diff domain web site (or) ip address
in asp.net 1.1/c#, can i do it thro' web.config (without compilation) or code? what are the options to do this? any adv/disadvantages using the suggested method?
I have two domains: www.MySite.ORG and www.MySite.COM. In both, there are web applications done in asp.net 4. I would like to modify the web.config of www.MySite.COM so that all the visitors going here will automatically be redirected to www.MySite.ORG. I thought I could do this through the control panel in the webhost, but it seems it cannot be done.
I'm going to be in a situation where I'll have www.DomainA.com and www.DomainB.com, each having seperate IPs. All requests to www.DomainB.com/{Path}, I'd like to redirect to www.DomainA.com/{Path}.
My initial reaction was, in the base directory, to simply create a HTTPModule and Web.config to add in the module, where the module would then redirect the request to DomainA.
The only problem with this is IIS is not executing the module, and instead determining itself whether or not there is a matching file or application to run based upon the requested path (i.e. so you'll either get an error about the requested file not existing, or a security error about not finding the requested application).
What do I need to change in IIS to always run my module? Or is there any easier way to do this using .Net 2.0 & IIS6?
I'm having an issue Redirecting to the same domain.
For example, the redirection takes place on ServerA.Domain.com/Folder/application.aspx. However, the program redirects me to ServerA/Folder/application.aspx.
The application works fine on this domain, but I'm forced to relogin.
What can I do to force the redirection to the same domain?
So far, I forget, that BeginRequest started only when file physically exist. how I can make such redirect in asp.net without creating hundreds of old pages?
I am browsing the page (http://jessie.mydomain.com/), then i click the Logout button in this page, it will be logout successful but it will not redirect to the page (http://www.mydomain.com/Default.aspx), it will show (http://jessie.mydomain.com/Default.aspx).
in MyWeb there are all the aspx page and some entites datamodel, in MyApp there are the class with function like "getter data from DB" and there is a entity data model.
afeter the deploy, I have only the web.config and the connection string for the entity datamodel....itīs run ok, read/write the data on the DB.
The problem is with MyApp.....after the deploy it is a dll file and I donīt have the app.config and the entity inside it donīt run, not read/write nothing on the DB.
There arenīt error or messager but not read/write the data in the MyApp project.
all run on the iis 7
now...the question is:
I lose the connection string (in app.config) after the deploy?
Can I put a entity in the MyWeb and read it in another project (myApp)?
I am developing web applicaiton. I want to read web.config in App.config file. I have appSettings and connectionStrings in web.config. How to read that?
I have a requirement that whenever a user logs onto a website using forms based authentication [FBA] that the site checks whether they have a related domain NT user record. There will be a matching lookup table between the ASPNETDB membership database and related domain accounts for users.Whenever an FBA user logs in and a related domain account is located then the member should be redirected to an alternative site / URL which is Windows NT authenticated rather than FBA. Before transferring them I would like to be able to pre authenticate them on the windows domain rather than an additional NT Login dialog box coming up and asking them to enter the related NT credentials.Is it possible to programatically preauthenticate using NT credentials before redirecting a user to an NT authenticated site?Note: This isn't technically a single sign on style scenario. The FBA / NT authenticated sites are not related other than the relationship between the original FBA credentials and the NT credentials lookup.
While using a third party dll I was getting the following exception - "exePath must be specified when not running inside a stand alone exe" with following trace
The reason I found was that it was looking for app.config and I had provided the details in web.config. My question is why does the system.configuration differentiate between web.config and app.config.