The correct approach to testing with IIS Express in these scenarios is to configure HTTP.sys to allow IIS Express running under standard permissions to perform the tasks. ![]() You can run IIS Express as an administrator to bypass these restrictions, but this is not a good practice for security reasons. This occurs because IIS Express does not have sufficient privileges to perform these types of tasks. Similarly, you might want to test your site using SSL or using a specific reserved port number.īy default, if you use IIS Express to test these scenarios, it reports a URL binding failure. For example, although IIS Express is not designed to be a production web server like IIS, you might need to test external access to your website. ![]() However, you might occasionally need to use IIS Express for testing scenarios that are not enabled by default. See Running IIS Express without Administrative Privileges for details. You can also test your website with SSL using a self-signed test certificate and a port in the range 44300 to 44399. For example, you can run a website locally using a non-reserved port. IIS Express was designed to allow the most common web development and testing tasks to be performed without administrative privileges.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |