Doorgaan naar de website
OCLC Support

ExcludeIP

  1. Laatst bijgewerkt
  2. Opslaan als pdf
Learn how to use the ExcludeIP config.txt directive to identify computers that have IP addresses known by your database vendors in EZproxy.

ExcludeIP (also written as E) is a position-dependent config.txt directive that interacts with AutoLoginIP and IncludeIP directives; database definitions; and other ExcludeIP directives.

ExcludeIP is used to identify computers that have IP addresses that are known by your database vendors and thus do not need to be proxied. It accepts a single parameter that is either an IP address or an IP address range.

AutoLoginIP and ExcludeIP are normally used to modify EZproxy's behavior for computers you manage, with ExcludeIP as the recommended and more commonly used option. AutoLoginIP is used in instances where a computer or group of computers must be proxied to be able to access a database, but where you do not need to challenge the user to authenticate first. ExcludeIP is used in instances where a computer or group of computers do not need to be proxied and the user should be redirected to the real URL, without a challenge for user authentication and without the user being proxied.

CIDR Notation

ExcludeIP accepts IP address ranges in CIDR notation. For example:

    ExcludeIP 192.168.0.0/16

Examples

 Example: local users bypass EZproxy

In this example, all machines in the IP address range of 192.168.0.0-192.168.255.255 are known to the vendor and users from these machines should be redirected to the real database URLs, bypassing EZproxy.

ExcludeIP 192.168.0.0-192.168.255.255

Title Some Database
URL http://www.somedb.com/
Domain somedb.com

Title Other Database
URL http://www.otherdb.com/
Domain otherdb.com

Example: everyone logs into e-reserves, local users bypass EZproxy for everything else

This example demonstrates setting up a local server with e-reserves where you want all users, both local and remote, to be required to authenticate before they can access the e-reserves server, but all other databases will bypass EZproxy. The key to this behavior is placing the e-reserves database definition prior to the first ExcludeIP directive.

Title E-reserves
URL http://ereserves.yourlib.org/
HJ ereserves.yourlib.org
ExcludeIP 192.168.0.0-192.168.255.255

Title Some Database
URL http://www.somedb.com/
Domain somedb.com

To make this configuration truly effective, the resource must be configured not to allow local users access, or else users can simply manipulate the URL and take EZproxy out of the path. When making such a change, you may want to allow select machines direct access, such as staff machines, but ensure that all other computers are blocked except for your EZproxy server.