October 5, 2009 at 17:29Managing a site on a Windows hosting or what to do if .htaccess does not work
It is far from a secret that when a site is running on Windows hosting under the control of the IIS web server, the directives located in the .htaccess file do not work, which allow you to control the settings of a site running under Apache.
Hosting control panels for the most part do not implement the site settings that the client may require for full work. Of course, manual tuning by the hoster staff of the client’s site on demand is not an option, but a crutch that you should not rely on.
To solve this problem, Microsoft released its solution - the IIS Manager program .
The program is less than two megabytes in size and allows you to remotely connect to the IIS web server and manage the site settings almost in the same way as it is available to the system administrator locally. Do not confuse it with a similar snap-in for server administrators. This is just a program that runs without IIS installed locally on any PC running Windows.
Returning to .htaccess, we note that in the case of IIS, the analogue of .htaccess is the web.config file, and IIS Manager is the graphical user interface for this (web.config) file.
At the same time, some of the settings from .htaccess can be imported into web.config:
learn.iis.net/page.aspx/5...o-iis-webconfig/
You can also import mod_rewrite rules using the built-in IIS Manager functionality
learn.iis.net/page.aspx/4...odrewrite-rules/
As a result, we find that for the hosting provider IIS Manager it is a safe means of managing the settings of IIS clients, the client cannot change the settings of the sites of other clients, only their sites , and for the client it is a powerful tool with a large list of features, among which are the following:
1. ASP.NET management, for example, setting the parameters for sending letters, parameters for connecting to databases.
2. URL Rewriting (mod_rewrite rules), creating rules for modifying URLs.
3. Handle mapping - setting the reaction of the server to file extensions.
4. You can change the authentication rules.
5. Request filtering - the ability to restrict access to files by extension, for example, you can make all files with the extensions .config and .inc inaccessible.
Five points is a short list, more settings are available, you can see the full list with us by activating access in the windows hosting control panel. This feature also works on the free demo period (by the way, the demo period is as long as 30 days).
PS Today we have become the Microsoft Gold Certified Partner. In just a year, it's pretty fast.
Congratulations are accepted. ;)
Hosting control panels for the most part do not implement the site settings that the client may require for full work. Of course, manual tuning by the hoster staff of the client’s site on demand is not an option, but a crutch that you should not rely on.
To solve this problem, Microsoft released its solution - the IIS Manager program .
The program is less than two megabytes in size and allows you to remotely connect to the IIS web server and manage the site settings almost in the same way as it is available to the system administrator locally. Do not confuse it with a similar snap-in for server administrators. This is just a program that runs without IIS installed locally on any PC running Windows.
Returning to .htaccess, we note that in the case of IIS, the analogue of .htaccess is the web.config file, and IIS Manager is the graphical user interface for this (web.config) file.
At the same time, some of the settings from .htaccess can be imported into web.config:
learn.iis.net/page.aspx/5...o-iis-webconfig/
You can also import mod_rewrite rules using the built-in IIS Manager functionality
learn.iis.net/page.aspx/4...odrewrite-rules/
As a result, we find that for the hosting provider IIS Manager it is a safe means of managing the settings of IIS clients, the client cannot change the settings of the sites of other clients, only their sites , and for the client it is a powerful tool with a large list of features, among which are the following:
1. ASP.NET management, for example, setting the parameters for sending letters, parameters for connecting to databases.
2. URL Rewriting (mod_rewrite rules), creating rules for modifying URLs.
3. Handle mapping - setting the reaction of the server to file extensions.
4. You can change the authentication rules.
5. Request filtering - the ability to restrict access to files by extension, for example, you can make all files with the extensions .config and .inc inaccessible.
Five points is a short list, more settings are available, you can see the full list with us by activating access in the windows hosting control panel. This feature also works on the free demo period (by the way, the demo period is as long as 30 days).
PS Today we have become the Microsoft Gold Certified Partner. In just a year, it's pretty fast.
Congratulations are accepted. ;)