When you first configure EZproxy, after logging in, you will see the default database menu page. One of the main purposes of this page is to introduce you to what a "starting point URL" looks like. If your EZproxy server is named ezproxy.yourlib.org, then the starting point URL that would be generated by the previous database definition is:
A "starting point URL" is a URL that can be placed on any web server, and can be used to access a specific database. When a user clicks on such a URL, EZproxy can detect if the user is local or remote, and if the user is remote, EZproxy can determine if the user has authenticated yet or not. If the user is local, EZproxy can redirect the user straight to the database, taking itself completely out of the loop. If the user is remote but has yet to authenticate, the user is authenticated first, then sent on to the database.
If "Some Database" introduces a new feature available directly at http://www.somedb.com/history/, you can use this information to create the new starting point URL:
Note that this URL does not match the URL in the database definition. This is perfectly acceptable, since the host name from this URL (www.somedb.com) exactly matches the host name from the URL in the database definition above.
A problem does arise if "Some Database" introduces another new URL such as http://find.somedb.com/everything/. Technically, the host name find.somedb.com matches against "Domain somedb.com" but if you try to use the starting point URL
EZproxy will generate an error indicating that you must add this line to config.txt:
As mentioned above, there can only be one URL line per database definition, and that URL line creates an implicit Host line for the host name in that URL. If you use other host names as starting points into other URLs provided by the same vendor, you must pre-authorize those other host names with a Host line. (This requirement that the host name in a starting point URL must match the host name in the URL line or a Host line is a security precaution.)