Site management on Windows hosting or how to be if .htaccess does not work
It’s not a secret that in the case of the site working on Windows hosting under the control of the IIS web server, directives placed in the .htaccess file that allow you to manage the settings of the site running under Apache do not work.
Hosting control panels for the most part do not implement those site settings that the client may need to complete the work. Of course, manual tuning by the client’s site hoster’s staff on demand is not an option, but a crutch on which you should not rely.
To solve this problem, Microsoft has released its solution - the program IIS Manager .
The program, which is less than two megabytes in size, allows you to remotely connect to the IIS web server and manage the site settings in much the same way as it is available to the system administrator locally. It should not be confused with a snap-in snap-in for server administrators. It is simply a program that works without locally installing IIS on any PC running Windows.
Returning to .htaccess, we note that in the case of IIS, the analog of .htaccess is the web.config file, and the IIS Manager is the graphical user interface to 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/
This includes importing mod_rewrite rules using IIS Manager built-in functionality.
learn.iis.net/page.aspx/4...odrewrite-rules/
')
As a result, for the hosting provider IIS Manager is a safe management tool for IIS client settings, the client cannot change the settings of other clients' sites, only its 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 server response to file extensions.
4. You can change the authentication rules.
5. Filtering requests - the ability to deny access to files by extensions, for example, you can make all files with .config and .inc extensions inaccessible.
Five points are a short list, more options are available, you can see the full list by activating access in the windows hosting control panel. This feature also works on a free demo period (by the way, the demo period lasts 30 days).
PS Today we have become Microsoft Gold Certified Partner. In just a year, it's pretty quick.
Congratulations are accepted. ;)
Hosting control panels for the most part do not implement those site settings that the client may need to complete the work. Of course, manual tuning by the client’s site hoster’s staff on demand is not an option, but a crutch on which you should not rely.
To solve this problem, Microsoft has released its solution - the program IIS Manager .
The program, which is less than two megabytes in size, allows you to remotely connect to the IIS web server and manage the site settings in much the same way as it is available to the system administrator locally. It should not be confused with a snap-in snap-in for server administrators. It is simply a program that works without locally installing IIS on any PC running Windows.
Returning to .htaccess, we note that in the case of IIS, the analog of .htaccess is the web.config file, and the IIS Manager is the graphical user interface to 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/
This includes importing mod_rewrite rules using IIS Manager built-in functionality.
learn.iis.net/page.aspx/4...odrewrite-rules/
')
As a result, for the hosting provider IIS Manager is a safe management tool for IIS client settings, the client cannot change the settings of other clients' sites, only its 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 server response to file extensions.
4. You can change the authentication rules.
5. Filtering requests - the ability to deny access to files by extensions, for example, you can make all files with .config and .inc extensions inaccessible.
Five points are a short list, more options are available, you can see the full list by activating access in the windows hosting control panel. This feature also works on a free demo period (by the way, the demo period lasts 30 days).
PS Today we have become Microsoft Gold Certified Partner. In just a year, it's pretty quick.
Congratulations are accepted. ;)
Source: https://habr.com/ru/post/71550/
All Articles