A collection of solutions to local publishing websites and HTTP error codes in VS2012/VS2013

This article mainly introduces in detail the problems encountered by the VS2012/VS2013 local publishing website and the solutions to the HTTP error codes. It has certain reference value. Interested friends can refer to it

HTTP error 500.19 Internal Server Error, HTTP error 403.14 Forbidden, HTTP error 404.17 Not Found, the solutions to the three problems are as follows

1. The configuration file cannot be read due to insufficient permissions

Solution: Right-click the website and select Edit Permissions. Security - Edit - Add - Advanced - Find Now - Everyone.

2. Missing website default page

Solution: This is because the default start page of the website is not set. Need to add a default start page in the default document. Right-click the default document - open functions - add, and enter the default start page name of the publishing website.

3. .net version is inconsistent

##Solution:

Enter the application pool interface

##In the application pool, right-click the website to be published-Advanced Settings - The .NET Framework version is set to v4.0

Of course, the website published in this way is only limited to mutual access within the local area network. , if you want to be able to access the external network, you can make relevant settings through routing and servers, which will not be discussed here.

The above is the detailed content of A collection of solutions to local publishing websites and HTTP error codes in VS2012/VS2013. For more information, please follow other related articles on the PHP Chinese website!