[Resolved] HTTP Error 403.14-Forbidden solution (WEB Development)

Error Figure:

Error 403 series:


403.1 error is due to "execute" access forbidden caused, if the attempt to execute CGI, ISAPI, or other executable program from the directory, but the directory will not allow such an error occurred while executing a program.

403.2 error is due to "read" access is prohibited caused. Directory causes this error because there is no default page available and directory browsing is not enabled for the directory, or to display an HTML page resides only marked as "executable" or "script" permissions.

403.3 error is due to "write" access is prohibited caused when trying to upload a file to a directory or modify files in the directory, but the directory does not allow "write" such an error occurs when accessing.

403.4 error is caused by requiring SSL, you must use "https" in the address of the page you want to view.


403.5 error is due to require the use of a Web browser 128-bit encryption algorithm caused, if your browser does not support 128-bit encryption algorithm this error occurs, you can connect to the Microsoft website to upgrade your browser.


403.6 error is due to IP address rejected caused. If there is not access the site's list of IP addresses, and IP addresses that you use the list server, you will return this error message.


403.7 error because the required client certificate, this error will be returned when the resource requirements needed to access the browser has the server to recognize the Secure Sockets Layer (SSL) client certificate.


403.8 error is due to prohibit access to the site caused, if there is a list of DNS names can not access the site server and the DNS name you use when such information will be returned in the list. Please note the difference between 403.6 and 403.8 errors.

403.9 is due to user error caused by too many connections, because the Web server is busy, it will return this error due to excessive traffic and unable to handle the request.

403.10 error is an error caused due to an invalid configuration, when you try to execute CGI, ISAPI, or other executable program from the directory, but the directory does not allow the implementation of the program will return this error.

403.11 error is due to password change caused by not authorized to view the page.

403.12 error is due Mapper denied access caused. To view the web page requires a valid client certificate, and your client certificate mapping does not have access will return Mapper denied access to this Web site errors.

403.13 error is due to the page you want to view requires the use of a valid client certificate to use client certificate has been revoked, or can not determine whether the certificate has been revoked due.

Error 403.14 Web server is configured to not list the contents of this directory, Directory Listing Denied.

403.15 error is due to client access licenses caused by too much, when the server exceeded its client returns this entry error when accessing licensing restrictions.

403.16 error is due to client certificate untrusted or invalid caused.

403.17 error is due to client certificate has expired or is not yet valid caused.

Error Analysis:

You may have encountered in the process of developing such a mistake might be encountered when IIS deployment, there are likely to be encountered during startup web program. We also see a lot of solutions. But some described more one-sided, did not find the source of the problem.

1, in fact, not difficult to find the error in fact it is mainly looking for the directory file, then the question is, why is it looking for the directory file it? The answer is: it does not start page . That is why it has to go to the directory file, which of course have to go find a catalog file.

2, there is the problem here? Why server file are listed in this directory it? The answer is: security issues, who will showcase their project files are out of it. As long as we find the root of the problem, then the solution to the problem of natural enough to say.

Solution:

1. No Home: We found the interface directly to the IIS default document - add your own default start page. Figure:

2. We find that it can browse the directory, but this is only for the development phase, after the line, the deployment must remove the set (security reasons)

<modules runAllManagedModulesForAllRequests="true"/>

3. simple and crude ways: directly enter the document name can be accessed in the address bar.

 

Published 133 original articles · won praise 70 · Views 100,000 +

Guess you like

Origin blog.csdn.net/whc888666/article/details/100760537