I have a website which has two domains added. Both domains point to the root of the website. Is it possible to alter the robots.txt so that one of the domains doesn't get crawled, while the other still does?
I have learned recently that I can stop Google bots looking at some pages via the robots.txt file.Great got that sorted out.However how can I stop the crawler or bot from scanning some text on my page. But reading other parts just fine.For example I have a large legal disclaimer on each page,and I have seen that via google web master tools that my keywords are all out of the disclaimer.Cant have that!
Can I turn off a control or label to crawlers eyes?? Any ideas..I cant move disclaimer to a single page as then it looses effect.
UDPATE: <!--googleoff: all-->Come to the fair!<!--googleon: all-->
This is how I added an email link on my page, but does .net have any built in tool for preventing Robots from finding this address? What is a good way to present an email link that wont be detected by spam robots?
So we have been using the same login gode to connect to various domains in asp.net, with and without MVC. The code works. We have a new server, first one to run server 2008 r2, set up with a directory structure similar to one of the ones that has been working. Using forms authentication, I set up in the web.config
It connects to build the membership provider just fine, but when I tryto use the exact same username and password to login on the forms login page (the stock asp.net stuff) it fails to login. same user, same password that's being used to connect with the membership provider. If I change the password in the web.config, I get an error that it's incorrect, so I know that the membership provider is getting connected with those credentials. What I can't figure out is why can't I use the same credentials to login? I've checked:
The user is not locked.
the user is not set to change password on next logon.
I want to redirect different domains which I have to my newly created website using dotnetnuke. As it is currently working on this site [URL](when user type thescripts.com it redirects user to [URL]
So I know you can share your cookies across subdomains eg. staging.mysite.com and www.mysite.com etc by setting the domain of the cookies to ".mysite.com"
BUT, is there a way to share across all the sub domains EXCEPT one. e.g. the cookies will not persist on images.mysite.com?
I have 2 applications. One on asp.net webforms [URL] which should provide authentication, user logs in and I can use the cookie to authenticate on my asp.net mvc app located at [URL]. All I'd like to do is able to access the cookie so I can get the userId that was stored in it using the FormsAuthentication.
They use normal authentication provided by microsoft;
I have a web app located at [URL] and I have several domains, such as [URL], [URL], etc. all pointing to the same directory in IIS. I use Host Headers to acheive this by setting the 'Host Header Values' under properties for the main site (under the Web site identification section). Based on the host header value I perform different functions in my pages.
Because of the way I have it set up, all the domains share the same files, web.config, etc. I have set the 'machinekey' in my web.config and have forms authemtication. However, when I go to MyMainSite.com and log in and then the user clicks a link and gets directed to MyFirstSite.com the user is shown as logged out. I need the user to be logged in and I need to be able to access the logged in user profile to display certain information. I thought by setting the 'machinekey', i could acheive this, but it does not seem to work.
how to go about having a single log on for my users?
The articles I have found show the same domain or have different domains each with a different web.config. The way they describe does not seem to work for me.
I would like to know the method of setting up sub-domains in the development environment. Don't have any hosting account yet. But would like to test it up internally by simulating a similar setup that would be provided by the hosting company later on.
We have an ASP.NET web application which uses integrated windows authentication. It is accessed by users from two domains, A and B. A is the primary domain and B is an older domain which is going away. Web application is authenticating users using a group policy which only exists in domain A. Every user in domain B has an account in domain A. The application lives in domain A. There was no trust between the domains. So users from domain A would get silently authenticated and logged into the site. Users from domain B didn't get authenticated automatically and were prompted with the IE popup, to which they authenticated using their domain A credentials and everything worked. Now somebody has set up a trust between the domains and users from domain B get authenticated silently to IIS, and then their login fails (no group policy). So the question is:
can I either programmatically or in IIS configuration make it so that users from domain B still get prompted even though there is trust between the domains? Is there a way to tell the server where IIS is running to ignore the trust relationship maybe?
I'm trying to redirect any non-www prefixed traffic to the www prefixed domain. I'm using Umbraco as the CMS and have added the following code into the urlrewritingnet config file:
Is it possible to have one asp.net web application that handles requests from two domains via asp.net routing? I need one TLD domain per language version pointing to the same app.
How to set up a route that recognize, if the request is coming from domain1.de or domain2.com? How to configure the domains DNS for this to work?
We are developing a SaaS application in Asp.net, where we have used the Single application and Per Tenant Database. The application is more like a Saas e-commerce where SSL and data separation are required features. Now we want that every Tenant can have his separate top level domain names instead of the second level domains like 37Signals. So all the domains abc.com and xyz.com are using the same single app.
What i need to know is how to implement and deploy the https in the application so that everything works out fine, also how should we configure the NameServer and web application on IIS so that all the domains are pointing to the one application.
I have a web application that dynamically loads assemblies based on database configuration entries to perform certain actions (dynamic plugin style architecture).The calls to the objects are in a Factory Pattern implementation, and the object is cached (in a static dictionary<> within the Factory) as the calls can be made many thousands of times in a minute.The calls to this factory are made from both the main web application and a number of webservices, some in different assemblies/projects.When I need to update one of these DLLs, I have to recycle IIS to get the DLL released.As this has an impact on another application on the server, I wanted to know if there was a way I could release the DLL without restarting IIS?
I try to send emails through ASP.NET interface and can't get it to work. Emails are sent, but only if the receiver of the email has the same domain name as my server (receiver@mydomain.com). The weird thing is, I actually CAN send such emails from any email program. So it seems that my Web.config file is missing something (?), although it looks ok (for me):
How to create subdomains in IIS? For example if i have 2 URLS - portal.ABC.com and product.ABC.com and both have different projects in visual studio.Net.
If i have to deploy them on the same server, how to map their URLs?
Also, is it possible to share the session information between both of them?
I am using a Network Solutions (NS) shared hosting account. When adding two domain names to my NS account I originally had my entire hosting folder "/htdoc/" assigned to my first domain. I was instructed by customer service to create a new sub folder for each domain and assign the domain names to each one using my NS account manager. Each website is its own application with vastly different settings At this point my directory looked like this:
It is an error to use a section registered as allowDefinition='MachineToApplication' beyond application level. This error can be caused by a virtual directory not being configured as an application in IIS
Naturally I called NS assuming that all they need to do was change a setting so that each sub folder would serve as the main directory for each site. Instead I was told that I need to configure /htdocs/ as its own application with a special web.config file configured to handle this in some way. Of course my next question was how do I configure the web.config to solve this problem and instead of answering the question they said that the question was outside the scope of their customer support.
What I need is simple. Code to add to a web.config with default settings in the /htdocs/ directory that specifies the sub directories as the parent directories for those websites and that no setting in any specifec site should have an effect on any others.