Top 10 principles of IIS

xiaoxiao2021-03-06  111

Top 10 principles of IIS

1. Custom Error Page Although the custom error page is simple, only a few administrators use it effectively. The administrator can map the HTTP error message to the absolute URL of the server or a file in the MMC, and more detailed information can be found here. If you are too trouble, you want a simpler method, or you want the developer to define the wrong page, and don't want them to have permissions using MMC, you can use tools like Customer Error.

2. Metabase research If you think the apache function is powerful because it has a configuration file, then you should look at the metabase of IIS. With Metabase, administrators can complete all jobs about IIS, for example, create a virtual directory; stop, start, or pause Web site; establish, delete, disable or enable applications. Microsoft provides a visual tool MetaEdit to help you read and write Metabase, you can download its latest version here. In order to use Metabase more effectively, you should try the command line interface - IIS Administration Script, referred to as Adsutil.vbs, you can find it in the C: / INETPUB / Adminscripts or% SystemRoot% / System32 / InetSrV / Adminsamples directory . Note: Metabase is very important to the normal work of the Web site, don't destroy it. Remember: You must back up before any modification.

3. Automatic correction of the URL spelling error Apache's helper always boasts some small features of Apache, where the coolest "automatic correction of URL spelling error", now, IIS administrators can also play these small features, Use UrlspellCheck to automatically correct the URL spelling error taking a dish. To make a test: www.urlspellcheck.com/fak.htm and www.urlspellcheck.com/faq1.htm, how, the second error spelling will be automatically corrected.

4. Holding URLS Apache's advocator has always boasts the powerful function of MOD_rewrite, now there is so much hit by such products for IIS, there are many more than mod_rewrite, because using mod_rewrite, you must be familiar with regular expressions. Try: IiSWRITE or ISAPI REWRITE.

5. Detecting a browser assumes that everyone's viewing site is as stupid as the same browser or screen size, you can use JavaScript to detect the visitor's browser. If you use IIS, you will have a better choice - Cyscape Company's Browserhawk, the Apache world has no products compared to it. Cyscape has recently launched a new product called Cuntryhawk, which can be used to detect the area where visitors are located (country). Unfortunately, I have no language sensitive or regionally sensitive content, I have not used it.

6. Site content compressed IIS 5 has a built-in compression function, can be said, it is simply deteriorating, using Pipeboost.

7. Web application Cache You can set different files or directories to expire, open the IIS information server, right click on the site content, click Properties, and you can set it accordingly in the form jumped. If you want the developer to set it yourself, please use the software of Cacheright, Xcache. Effectively use the cache to spend some time and money, but when you see the number of visitors, you can get a small number of 304 responses, and the bandwidth flow is also greatly dropped, you will experience Why do you have to do this. There are not many sites that have a good cache. On the contrary, the article about it is much like a cattle on the Internet, take a look at these: Brian Davidson's Page, Mark NOTTINGHAM, and What Aol Has To Say. 8. Tuning Server Tuning Server is not a small topic, requires a monograph to explain it. There are some good base tutors and help online, such as Brett Hill and Microsoft's own Knowledge Base Article. Of course, if you don't want to spend these time, use this --xtune.

9. The security of the security now is now a lot of people who attack the site, but as long as you are willing to pay a little effort, you will not be a fool who will only take a beaten. Finding your server information and operating system information is the first target of the attacker, so, first, don't expose your http head to let others know that you are IIS, use the servermask software to remove or replace the http header . Second, you can further install your server environment by deleting unnecessary file extensions. In addition, you can also scan a problematic URL request, Microsoft provides you with a free tool --urscan.

10. Patch, patch, patch! You should download the latest patch installation. You can go to Microsoft's site, you can also go to http://www.cert.org/, use IIS as a keyword query. Ok, this is the IIS management 10 I summarized. These 10 are not necessary in IIS 6, but for W2K and NT IIS administrators, this 10 can make you sleep well on a good night.

转载请注明原文地址:https://www.9cbs.com/read-126924.html

New Post(0)