From the Web Cache menu, select Administration Ports Configuration.

Getting Started with Administering Oracle Web Cache 2-25 Routing Enabled Click to permit Oracle Web Cache to route requests to the origin server or leave unchecked to only serve requests from cache. Oracle recommends not selecting this option if temporary maintenance of an origin server is needed. Oracle Web Cache tries to route a request matching a particular site to all origin servers mapped to that site. If all of the origin servers have Routing Enabled not selected, Oracle Web Cache serves a network error page to clients. See Section 2.11.6 for further information about configuring error pages. Failover Threshold Enter the number of allowed continuous read and write failures with an origin server on established connections. The default is five request and response failures. If any connection failure occurs, Oracle Web Cache immediately considers an origin server down. When the threshold is met, Oracle Web Cache considers the origin server down and performs automatic failover of the origin servers. If an origin server fails at any time after Oracle Web Cache has started to send a request, then Oracle Web Cache increments the failure counter. The failure counter is reset if there is a successful server response. A request is considered failed if: ■ There are any network errors other than connection failure errors. ■ The HTTP response status code is something other than 1xx, 2xx, 3xx, 4xx, 501 Not Implemented, and 505 HTTP Version Not Supported. After the threshold is met, Oracle Web Cache considers the server down and uses other servers for future requests. Oracle Web Cache starts polling the down server, by sending requests to the URL specified in the Ping URL field. When Oracle Web Cache receives a successful response from the server without any network errors and the HTTP response code is not less than 100, or not equal to 500, 502, 503, 504, Oracle Web Cache considers the server up again and uses it for future requests. Notes: ■ The threshold does not apply if Oracle Web Cache cannot connect to an origin server. In this case, Oracle Web Cache immediately considers the server down and does not use it for future requests. If there are other origin servers, Oracle Web Cache retries the request to another origin server. If there no servers configured, Oracle Web Cache returns an error. ■ The failover to another origin server does not apply if there is only one origin server left. Table 2–9 Cont. Create Origin Server Element Description