Shulou(Shulou.com)06/01 Report--

This article shows you how to solve the 403.9 error of HTTP under XP-the problem of forbidding access, the content is concise and easy to understand, it will definitely brighten your eyes. I hope you can get something through the detailed introduction of this article.

There are a lot of solutions on the Internet, here are two, but the really most effective solution is the second. The reason for bringing up the first is that it is possible that the reason why your IIS has such a problem needs the first way to solve it completely. The second method is to clearly point out that it is the problem with your program, which can easily occur when debugging the program.

The first kind:

My own machine is Windows XP system.

A self-developed program is deployed on this machine.

It is not smooth to use IIS when testing, and the error page with more than the limit of connection often appears in the test.

So I'm going to change the limit on the number of connections in this IIS. Since XP's IIS does not provide the performance tab itself, I have to start from other aspects.

As it happens, Microsoft itself happens to provide this gadget, and it is estimated that they have also felt these problems.

A gadget for managing IIS from Microsoft, called MetaEdit

The download address is:

Http://download.microsoft.com/download/iis50/Utility/5.0/NT45/EN-US/MtaEdt22.exe

Then, execute MtaEdt22.exe and follow the wizard prompts to complete the MetaEdit installation.

After installing MetaEdit, click MetaEdit2.2 to run under the program group AdministrativeTools on the start menu

Window appears: expand the tree to LM-W3SVC on the left side of the window

Click directly on the W3SVC folder and select the item in the list on the right whose Name is MaxConnections

After double-clicking, a dialog box appears: in the last Data text box, the default is 10, and you change it to-1 without limit.

This is the maximum number of client connections set by default for WindowsXP Professional IIS. I directly changed it to 1000, which is the same as the server version of IIS.

So we can get back to work!

Other HTTP error messages:

HTTP 400-invalid request

HTTP 401.1-unauthorized: login failed

HTTP 401.2-unauthorized: login failed due to server configuration problem

HTTP 401.3-ACL prohibits access to resources

HTTP 401.4-unauthorized: authorization denied by filter

HTTP 401.5-unauthorized: ISAPI or CGI authorization failed

HTTP 403-access prohibited

HTTP 403-access to Internet Service Manager (HTML) is limited to Localhost

HTTP 403.1 No access: no executable access

HTTP 403.2-No access: no read access

HTTP 403.3-No access: no write access

HTTP 403.4-access prohibited: SSL required

HTTP 403.5-access prohibited: SSL 128is required

HTTP 403.6-access prohibited: IP address denied

HTTP 403.7-access prohibited: customer certificate required

HTTP 403.8-No access: no site access

HTTP 403.9-access prohibited: too many connected users

HTTP 403.10-access prohibited: invalid configuration

HTTP 403.11-access prohibited: password change

HTTP 403.12-access prohibited: access denied by the mapper

HTTP 403.13-access prohibited: customer certificate has been revoked

HTTP 403.15-access prohibited: too many customer access licenses

HTTP 403.16-access prohibited: customer certificate is untrusted or invalid

HTTP 403.17-access prohibited: the customer certificate has expired or is not yet valid

HTTP 404.1-Web site could not be found

HTTP 404-File cannot be found

HTTP 405-Resources are prohibited

HTTP 406-unacceptable

HTTP 407-Agent authentication required

HTTP 410-never available

HTTP 412-prerequisite failed

HTTP 414-request-URI too long

HTTP 500-Internal server error

HTTP 500.100-Internal Server error-ASP error

HTTP 500-11 server shutdown

HTTP 500-12 application restart

HTTP 500-13-Server too busy

HTTP 500-14-invalid application

HTTP 500-15-request for global.asa is not allowed

Error 501-not implemented

HTTP 502-Gateway error

The second kind:

The 403.9 error is caused by too many connected users, which is returned when the Web server is too busy to process the request due to too much traffic.

Solution: 1. The key is that there is an endless loop in your program, or there are errors on eof and bof. Iis will say this when the data submitted is too large. Look at the program on your page, which is really not on the user's connection. Restarting iis can solve this problem: enter iisreset in "run"

The above content is how to solve the 403.9 error of HTTP under XP-the problem of forbidding access, have you learned the knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.