Control website access

Each FrontPage Web (including each sub-Web) contains three isapi dll copies that constitute FrontPage Server Extensions. These DLL files are generated in the directory under the top-level directory of FrontPage Web.
▲_ Vti_bin/_ vti_adm/admin. dll is used to complete Web management tasks.
▲_ Vti_bin/_ vti_aut/author. dll is used to compile FrontPage Web
▲_ Vti_bin/shtml. dll: Behavior During browsing
FrontPage sends the http post request to these DLL for all compilation and management. The FrontPage Server is extended and stored in an independent directory under the root directory of the user file.
HTTP is a stateless protocol. IIS processes each HTTP request independently. For example, when an HTTP request accesses the Admin of a website from FrontPage Explorer. dll, IIS tries to run the request in the way of anonymous user IUSER_hostname. Can IIS execute Admin. there are many reasons for dll processing requests:
(1) IIS may not allow enabling anonymous browsing
(2) the directory containing Admin. dll is not set as unexecutable by IIS
(3) the IUSR_hostname user may not exist in Windows NT (created by IIS during installation), or this user is disabled after IIS installation.
(4) the ACL of Admin. dll may not grant the permission to the IUSR_hostname execution file.
If the anonymous user cannot execute Admin. dll, the Web server will return error 401 (access prohibited). Then, FrontPage Explorer prompts the viewer to provide the user name and password, and uses Windows NT to authenticate the user, the user may not see this prompt, just as the visitor only provides the security ID of the login user, after the user is identified, IIS will attempt to use the account provided by the user to perform operations again, if the authenticated user has the Admin. dll permission, then this user can become the FrontPage administrator and perform appropriate operations.
In practice, because FrontPage Explorer can cache the username and password when the initial prompt is sent, it does not require the user to provide the username and password for each HTTP request. However, if the cached user name and password do not have sufficient permission to execute the operation, you are prompted to enter a new user name and password.
Even if the FrontPage and IIS settings are correct, the user may be prohibited from accessing the FrontPage site, depending on the user account status. If the Windows NT user no longer exists or has been disabled, or the isapi dll cannot be executed, and these users will be denied access.
This article is prepared by the beach kiddies. You can reprint it, but please indicate its source. Thank you!