All files, except the EZproxy program, are created automatically during the installation process. EZproxy uses the following files:
|This binary file is the actual EZproxy program.
|This user editable text file contains configuration directives, including information on your licensed databases. In EZproxy 5.0 and earlier, this file was named ezproxy.cfg.
|This user editable text file contains user authentication information. At its simplest, this file contains usernames and passwords. In EZproxy 5.0 and earlier, this file was named ezproxy.usr.
|This text file is a record of proxy server usage in the NCSA web server log file format. If used with standard web log analysis software, this file can provide information on the volume of remote use.
|This text file is a record of certain informational and error conditions that occurred when EZproxy was running. In EZproxy 5.0 and earlier, this file was named ezproxy.msg.
|This text file contains information on active users and virtual web server proxies.
|This text file is the EZproxy licensing agreement.
The following user editable HTML files that are located in docs subdirectory:
|EZproxy uses a domain-based cookie as its ongoing verification that a user has authenticated. If the remote user disallows the cookie, the contents of this file are sent to explain the reason why the cookie is required.
|When the built-in user validation feature is used, this web page is sent to the remote user to prompt for authentication.
|If the user does not successfully authenticate to the login.htm page, the user is sent this page.
|When the user logs out from EZproxy, this web page is sent to confirm the logout.
|This web page provides a basic menu of databases. In most instances, this file is only used for testing purposes. For production use, you are more likely to create URLs in remote documents that look like http://ezproxy.yourlib.org:2048/login?url=http://somedb.com which users will then use to connect to remote databases.
Tags recommended by the template: article:topic