Is there a good way of remotely managing 301 redirects in IIS? I have recently taken ownership of a small retail ASP.NET website I've been tasked with providing our SEO provider the ability to change redirects for old products etc without having direct access to the server, or needing us to make the change.
The website is ASP.NET 4.0, running on Windows Server 2008 with IIS 7.
you could maintain a list of the required redirects via an app.config file - have a module which takes the request and checks the request against the file
if there is a match then you could redirect to a known place. The trouble is that it could be a little slow - instead of a config file you could store the redirects in the database as an alternative
Related
We are facing a weird issue specific only on one website even though we are hosting more than 150 websites on same server using Kentico CMS 11.
We have turned on "www" prefix settings from Kentico -> Urls & SEO for all the websites and all these sites are working without any issue.
But there is a specific website on which all the requests are getting redirected to home page if try to access with "www" prefix.
I have tried checking at code level and could not find any issue. If it would be code issue then it should appear for other websites as well.
We are using Azure app service for hosting our application so I have checked in application insight as well and could not get any lead as all the request which are logged for this specific websites are of home page.
Please help me in understanding if I need to see through this issue at some other place. I have checked with Client's IS team and they could not find any DNS settings difference when compared to other websites which are working fine.
Please check the web.config file of this site. It may contain a wrong URL redirect associated with "www" so that probably this redirect just cuts all the path from URL.
I am about to migrate/move the data from a Windows Plesk server to a Linux Plesk server. Which in itself is a humongous pain in the a***!
On top of that I am developing a new version of a website on the current WPlesk(Windows Plesk). It is being developed in Wordpress. The current website is running a system called nemCMS, which requires a WPlesk to run.
When I move the data and domain to the new LPlesk(Linux Plesk), will I then be able to set up the htaccess redirects from the old - now non existing nemCMS site & URLs - without losing page rank etc.?
I hope you are able to help me out!
Thanks!
Officially migration from WPlesk to LPlesk and vice versa is not supported. You can do it only with creation the same domain/hosting on destination server and migration site content manually. Be sure that site is not connected to any Windows only web technologies :)
For redirection you can just change type of hosting for domain on WPlesk to Forwarding.
We want to avoid our own users from hotlinking to images and media outside our own domain. Is there a way to do this through IIS (version 8 on Windows Server 2012) ? We have the URL Rewrite module installed, but unsure how to develop a rule that would accomplish what we need.
Pleaes keep in mind I'm wanting to block any hotlinking to other websites, and only allow images/media that are located on our own domain. Googling and searching here on stackoverflow results in preventing other sites from hotlinking to one's own self hosted content, not the other way around like we want.
WMSAuth plugin for Windows Media Services might be something which you might look at. It's not for IIS but you might use the same concept for building your solution.
It's open source so you can check the sources on github.
I have a folder in which all asp files are protected by including validate.asp (which presents a login if the session is not validated and ends the response, otherwise it allows the page to display.
How can I protect non-asp content?
The Site is running under Windows 2003 Server with IIS 6.0
#My Other Me: check out ISAPI Rewrite
ISAPI_Rewrite is a powerful URL manipulation engine based on regular expressions. It acts mostly like Apache's mod_Rewrite, but is designed specifically for Microsoft's Internet Information Server (IIS). ISAPI_Rewrite is an ISAPI filter written in pure C/C++ so it is extremely fast. ISAPI_Rewrite gives you the freedom to go beyond the standard URL schemes and develop your own scheme.
Alternatively, you can also check out IIS Password
IISPassword password protects web sites that are hosted on Microsoft IIS, without using system user accounts. IISPassword protects complete web sites, subfolders or even certain files or file types. When trying to access a password protected object, the user is asked to log in through a dialog box ..
ISAPI Rewrite has a lite version and IISPassword has a trial version, so you can try out both for free to see if they could suit your needs.
Note: I originally posted this on ServerFault, but I haven't gotten any responses at all. Since it looks like I'm on track to get the Tumbleweed badge over there, I figured I would try here also.
Our existing public website consists of a mish-mash of asp.net pages with mostly static content and some real web applications that are set up as virtual directories. We're now looking at installing Umbraco, which requires that you install it at the root of the website.
Since the CMS would be at the root of the website, I'm assuming it's a bad idea to run our existing pages and web applications underneath Umbraco (due to the URL rewriting it performs and inheriting web.config settings, etc.) So how do we make everything co-exist peacefully both while we transition to the CMS and after we're finished?
My only idea so far was to set up the CMS and the applications as separate websites and then use some sort of URL rewriting/reverse proxy to make everything resolve correctly:
* www.example.com would keep resolving to our old homepage
* www.example.com/dept1 would keep resolving to the old dept1 page
* www.example.com/dept2 would resolve to the new dept2 page on the CMS
* www.example.com/app would resolve to an existing web application
We ending up setting up Umbraco as it's own website in IIS and then we bought ISAPI Rewrite so that we could seamlessly pass through CMS content for certain URLs.