| Home >> All >> org >> apache >> catalina >> [ valves Javadoc ] |
• org.apache.catalina.valves: Javadoc index of package org.apache.catalina.valves.
Package Samples:
• org.apache.catalina.valves
Classes:
• ExtendedAccessLogValve: An implementation of the W3c Extended Log File Format. See http://www.w3.org/TR/WD-logfile.html for more information about the format. The following fields are supported: c-dns : Client hostname c-ip : Client ip address bytes : bytes served cs-method : request method cs-uri : The full uri requested cs-uri-query : The query string cs-uri-stem : The uri without query string date : The date in yyyy-mm-dd format for GMT s-dns : The server dns entry s-ip : The server ip address cs(XXX) : The value of header XXX from client to server sc(XXX) : The value of header XXX from server to client sc-status : ...
• AccessLogValve: Implementation of the Valve interface that generates a web server access log with the detailed line contents matching a configurable pattern. The syntax of the available patterns is similar to that supported by the Apache mod_log_config module. As an additional feature, automatic rollover of log files when the date changes is also supported. Patterns for the logged message may include constant text or any of the following replacement strings, for which the corresponding information from the specified Response is substituted: %a - Remote IP address %A - Local IP address %b - Bytes sent, excluding ...
• JDBCAccessLogValve: This Tomcat extension logs server access directly to a database, and can be used instead of the regular file-based access log implemented in AccessLogValve. To use, copy into the server/classes directory of the Tomcat installation and configure in server.xml as: <Valve className="AccessLogDBValve" driverName=" your_jdbc_driver " connectionURL=" your_jdbc_url " pattern="combined" resolveHosts="false" /> Many parameters can be configured, such as the database connection (with driverName and connectionURL ), the table name ( tableName ) and the field names (corresponding to the get/set method ...
• RequestFilterValve: Implementation of a Valve that performs filtering based on comparing the appropriate request property (selected based on which subclass you choose to configure into your Container's pipeline) against a set of regular expressions configured for this Valve. This valve is configured by setting the allow and/or deny properties to a comma-delimited list of regular expressions (in the syntax supported by the jakarta-regexp library) to which the appropriate request property will be compared. Evaluation proceeds as follows: The subclass extracts the request property to be filtered, and calls the common ...
• FastCommonAccessLogValve: Implementation of the Valve interface that generates a web server access log with the detailed line contents matching either the common or combined patterns. As an additional feature, automatic rollover of log files when the date changes is also supported. Conditional logging is also supported. This can be done with the condition property. If the value returned from ServletRequest.getAttribute(condition) yields a non-null value. The logging will be skipped.
• RequestDumperValve: Implementation of a Valve that logs interesting contents from the specified Request (before processing) and the corresponding Response (after processing). It is especially useful in debugging problems related to headers and cookies. This Valve may be attached to any Container, depending on the granularity of the logging you wish to perform.
• ValveBase: Convenience base class for implementations of the Valve interface. A subclass MUST implement an invoke() method to provide the required functionality, and MAY implement the Lifecycle interface to provide configuration management and lifecycle support.
• ErrorReportValve: Implementation of a Valve that outputs HTML error pages. This Valve should be attached at the Host level, although it will work if attached to a Context. HTML code from the Cocoon 2 project.
• PersistentValve: Valve that implements the default basic behavior for the StandardHost container implementation. USAGE CONSTRAINT : To work correctly it requires a PersistentManager.
• SemaphoreValve: Implementation of a Valve that limits concurrency. This Valve may be attached to any Container, depending on the granularity of the concurrency control you wish to perform.
• RemoteAddrValve: Concrete implementation of RequestFilterValve that filters based on the string representation of the remote client's IP address.
• RemoteHostValve: Concrete implementation of RequestFilterValve that filters based on the remote client's host name.
• Constants: Manifest constants for the org.apache.catalina.valves package.
• FieldInfo: A simple helper for decoding the pattern.
| Home | Contact Us | Privacy Policy | Terms of Service |