archive-es.com » ES » E » EPPA.ES

Total: 100

Choose link from "Titles, links and description words view":

Or switch to "Titles and links view".
  • Apache Tomcat 7 Configuration Reference (7.0.22) - The AJP Connector
    incoming connection requests when all possible request processing threads are in use Any requests received when the queue is full will be refused The default value is 100 acceptorThreadCount The number of threads to be used to accept connections Increase this value on a multi CPU machine although you would never really need more than 2 Also with a lot of non keep alive connections you might want to increase this value as well Default value is 1 address For servers with more than one IP address this attribute specifies which address will be used for listening on the specified port By default this port will be used on all IP addresses associated with the server A value of 127 0 0 1 indicates that the Connector will only listen on the loopback interface bindOnInit Controls when the socket used by the connector is bound By default it is bound when the connector is initiated and unbound when the connector is destroyed If set to false the socket will be bound when the connector is started and unbound when it is stopped clientCertProvider When client certificate information is presented in a form other than instances of java security cert X509Certificate it needs to be converted before it can be used and this property controls which JSSE provider is used to perform the conversion For example it is used with the AJP connectors the HTTP APR connector and with the org apache catalina valves SSLValve If not specified the default provider will be used connectionLinger The number of seconds during which the sockets used by this Connector will linger when they are closed If not specified the JVM default will be used connectionTimeout The number of milliseconds this Connector will wait after accepting a connection for the request URI line to be presented The default value is 60000 i e 60 seconds executor A reference to the name in an Executor element If this attribute is set and the named executor exists the connector will use the executor and all the other thread attributes will be ignored Note that if a shared executor is not specified for a connector then the connector will use a private internal executor to provide the thread pool keepAliveTimeout The number of milliseconds this Connector will wait for another AJP request before closing the connection The default value is to use the value that has been set for the connectionTimeout attribute maxConnections The maximum number of connections that the server will accept and process at any given time When this number has been reached the server will not accept any more connections until the number of connections falls below this value The operating system may still accept connections based on the acceptCount setting Default value varies by connector type For BIO the default is the value of maxThreads For NIO the default is 10000 For APR native the default is 8192 Note that for APR native on Windows the configured value will be reduced to the highest multiple of 1024 that is less than or equal to maxConnections This is done for performance reasons maxThreads The maximum number of request processing threads to be created by this Connector which therefore determines the maximum number of simultaneous requests that can be handled If not specified this attribute is set to 200 If an executor is associated with this connector this attribute is ignored as the connector will execute tasks using the executor rather than an internal thread pool minSpareThreads The minimum number of threads always kept running If not specified the default of 10 is used packetSize This attribute sets the maximum AJP packet size in Bytes The maximum value is 65536 It should be the same as the max packet size directive configured for mod jk Normally it is not necessary to change the maximum packet size Problems with the default value have been reported when sending certificates or certificate chains The default value is 8192 If set to less than 8192 then the setting will ignored and the default value of 8192 used processorCache The protocol handler caches Processor objects to speed up performance This setting dictates how many of these objects get cached 1 means unlimited default is 200 If not using Servlet 3 0 asynchronous processing a good default is to use the same as the maxThreads setting If using Servlet 3 0 asynchronous processing a good default is to use the larger of maxThreads and the maximum number of expected concurrent requests synchronous and asynchronous requiredSecret Only requests from workers with this secret keyword will be accepted tcpNoDelay If set to true the TCP NO DELAY option will be set on the server socket which improves performance under most circumstances This is set to true by default threadPriority The priority of the request processing threads within the JVM The default value is java lang Thread NORM PRIORITY See the JavaDoc for the java lang Thread class for more details on what this priority means tomcatAuthentication If set to true the authentication will be done in Tomcat Otherwise the authenticated principal will be propagated from the native webserver and used for authorization in Tomcat The default value is true Java TCP socket attributes The BIO and NIO implementation support the following Java TCP socket attributes in addition to the common Connector and HTTP attributes listed above Attribute Description socket rxBufSize int The socket receive buffer SO RCVBUF size in bytes JVM default used if not set socket txBufSize int The socket send buffer SO SNDBUF size in bytes JVM default used if not set socket tcpNoDelay bool This is equivalent to standard attribute tcpNoDelay socket soKeepAlive bool Boolean value for the socket s keep alive setting SO KEEPALIVE JVM default used if not set socket ooBInline bool Boolean value for the socket OOBINLINE setting JVM default used if not set socket soReuseAddress bool Boolean value for the sockets reuse address option SO REUSEADDR JVM default used if not set socket soLingerOn bool Boolean

    Original URL path: http://ticket.eppa.es/docs/config/ajp.html (2015-09-25)
    Open archived version from archive


  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Context Container
    xml used for a web application to be logged at INFO level when the application starts The effective web xml is the result of combining the application s web xml with any defaults configured by Tomcat and any web fragment xml files and annotations discovered If not specified the default value of false is used override Set to true to ignore any settings in both the global or Host default contexts By default settings from a default context will be used but may be overridden by a setting the same attribute explicitly for the Context path The context path of this web application which is matched against the beginning of each request URI to select the appropriate web application for processing All of the context paths within a particular Host must be unique If you specify a context path of an empty string you are defining the default web application for this Host which will process all requests not assigned to other Contexts This attribute must only be used when statically defining a Context in server xml In all other circumstances the path will be inferred from the filenames used for either the xml context file or the docBase Even when statically defining a Context in server xml this attribute must not be set unless either the docBase is not located under the Host s appBase or both deployOnStartup and autoDeploy are false If this rule is not followed double deployment is likely to result preemptiveAuthentication When set to true and the user presents credentials for a resource that is not protected by a security constraint if the authenticator supports preemptive authentication the standard authenticators provided with Tomcat do then the user credentials will be processed If not specified the default of false is used privileged Set to true to allow this context to use container servlets like the manager servlet Use of the privileged attribute will change the context s parent class loader to be the Server class loader rather than the Shared class loader Note that in a default installation the Common class loader is used for both the Server and the Shared class loaders reloadable Set to true if you want Catalina to monitor classes in WEB INF classes and WEB INF lib for changes and automatically reload the web application if a change is detected This feature is very useful during application development but it requires significant runtime overhead and is not recommended for use on deployed production applications That s why the default setting for this attribute is false You can use the Manager web application however to trigger reloads of deployed applications on demand resourceOnlyServlets Comma separated list of Servlet names as used in WEB INF web xml that expect a resource to be present Ensures that welcome files associated with Servlets that expect a resource to be present such as the JSP Servlet are not used when there is no resource present This prevents issues caused by the clarification of welcome file mapping in section 10 10 of the Servlet 3 0 specification If the org apache catalina STRICT SERVLET COMPLIANCE system property is set to true the default value of this attribute will be the empty string else the default value will be jsp sessionCookieDomain The domain to be used for all session cookies created for this context If set this overrides any domain set by the web application If not set the value specified by the web application if any will be used sessionCookieName The name to be used for all session cookies created for this context If set this overrides any name set by the web application If not set the value specified by the web application if any will be used or the name JSESSIONID if the web application does not explicitly set one sessionCookiePath The path to be used for all session cookies created for this context If set this overrides any path set by the web application If not set the value specified by the web application will be used or the context path used if the web application does not explicitly set one To configure all web application to use an empty path this can be useful for portlet specification implementations set this attribute to in the global CATALINA BASE conf context xml file sessionCookiePathUsesTrailingSlash Some browsers such as IE will send a session cookie for a context with a path of foo with a request to foobar To prevent this Tomcat will add a trailing slash to the path associated with the session cookie so in the above example the cookie path becomes foo However with a cookie path of foo IE will no longer send the cookie with a request to foo This should not be a problem unless there is a servlet mapped to In this case this feature will need to be disabled The default value for this attribute is true To disable this feature set the attribute to false swallowAbortedUploads Set to false if Tomcat should not read any additional request body data for aborted uploads and instead abort the client connection This setting is used in the following situations the size of the request body is larger than the maxPostSize configured in the connector the size limit of a MultiPart upload is reached the servlet sets the response status to 413 Request Entity Too Large Not reading the additional data will free the request processing thread more quickly Unfortunately most HTTP clients will not read the response if they can not write the full request The default is true so additional data will be read Note if an error occurs during the request processing that triggers a 5xx response any unread request data will always be ignored and the client connection will be closed once the error response has been written swallowOutput If the value of this flag is true the bytes output to System out and System err by the web application will be redirected to the web application logger If not specified the default value of the flag is false tldNamespaceAware If the value of this flag is true the TLD files XML validation will be namespace aware If you turn this flag on you should probably also turn tldValidation on If the org apache catalina STRICT SERVLET COMPLIANCE system property is set to true the default value of this attribute will be true else the default value will be false Setting this attribute to true will incur a performance penalty tldValidation If the value of this flag is true the TLD files will be XML validated on context startup If the org apache catalina STRICT SERVLET COMPLIANCE system property is set to true the default value of this attribute will be true else the default value will be false Setting this attribute to true will incur a performance penalty useHttpOnly Should the HttpOnly flag be set on session cookies to prevent client side script from accessing the session ID Defaults to true wrapperClass Java class name of the org apache catalina Wrapper implementation class that will be used for servlets managed by this Context If not specified a standard default value will be used xmlNamespaceAware If the value of this flag is true the validation of XML files will be namespace aware If you turn this flag on you should probably also turn xmlValidation on If the org apache catalina STRICT SERVLET COMPLIANCE system property is set to true the default value of this attribute will be true else the default value will be false Setting this attribute to true will incur a performance penalty xmlValidation If the value of this flag is true the XML files will be validated on context startup If the org apache catalina STRICT SERVLET COMPLIANCE system property is set to true the default value of this attribute will be true else the default value will be false Setting this attribute to true will incur a performance penalty Standard Implementation The standard implementation of Context is org apache catalina core StandardContext It supports the following additional attributes in addition to the common attributes listed above Attribute Description addWebinfClassesResources This attribute controls if in addition to static resources being served from META INF resources inside web application JAR files static resources are also served from WEB INF classes META INF resources This only applies to web applications with a major version of 3 or higher Since this is a proprietary extension to the Servlet 3 specification it is disabled by default To enable this feature set the attribute to true aliases This attribute provides a list of external locations from which to load resources for this context The list of aliases should be of the form aliasPath1 docBase1 aliasPath2 docBase2 where aliasPathN must include a leading and docBaseN must be an absolute path to either a war file or a directory A resource will be searched for in the first docBaseN for which aliasPathN is a leading path segment of the resource If there is no such alias then the resource will be searched in the usual way Using as an aliasPath is not allowed Consider using docBase instead These external locations will not be emptied if the context is un deployed allowLinking If the value of this flag is true symlinks will be allowed inside the web application pointing to resources outside the web application base path If not specified the default value of the flag is false NOTE This flag MUST NOT be set to true on the Windows platform or any other OS which does not have a case sensitive filesystem as it will disable case sensitivity checks allowing JSP source code disclosure among other security problems antiJARLocking If true the Tomcat classloader will take extra measures to avoid JAR file locking when resources are accessed inside JARs through URLs This will impact startup time of applications but could prove to be useful on platforms or configurations where file locking can occur If not specified the default value is false antiJARLocking is a subset of antiResourceLocking and therefore to prevent duplicate work and possible issues only one of these attributes should be set to true at any one time antiResourceLocking If true Tomcat will prevent any file locking This will significantly impact startup time of applications but allows full webapp hot deploy and undeploy on platforms or configurations where file locking can occur If not specified the default value is false antiJARLocking is a subset of antiResourceLocking and therefore to prevent duplicate work and possible issues only one of these attributes should be set to true at any one time Please note that setting this to true has some side effects including the disabling of JSP reloading in a running server see Bugzilla 37668 Please note that setting this flag to true in applications that are outside the appBase for the Host the webapps directory by default will cause the application to be deleted on Tomcat shutdown You probably don t want to do this so think twice before setting antiResourceLocking true on a webapp that s outside the appBase for its Host cacheMaxSize Maximum size of the static resource cache in kilobytes If not specified the default value is 10240 10 megabytes cacheObjectMaxSize Maximum size of the static resource that will be placed in the cache If not specified the default value is 512 512 kilobytes If this value is greater than cacheMaxSize 20 it will be reduced to cacheMaxSize 20 cacheTTL Amount of time in milliseconds between cache entries revalidation If not specified the default value is 5000 5 seconds cachingAllowed If the value of this flag is true the cache for static resources will be used If not specified the default value of the flag is true clearReferencesHttpClientKeepAliveThread If true and an sun net www http HttpClient keep alive timer thread has been started by this web application and is still running Tomcat will change the context class loader for that thread from the current WebappClassLoader to WebappClassLoader parent to prevent a memory leak Note that the keep alive timer thread will stop on its own once the keep alives all expire however on a busy system that might not happen for some time If not specified the default value of true will be used clearReferencesStatic If true Tomcat attempts to null out any static or final fields from loaded classes when a web application is stopped as a work around for apparent garbage collection bugs and application coding errors There have been some issues reported with log4j when this is true Applications without memory leaks using recent JVMs should operate correctly with this attribute set to false If not specified the default value of false will be used clearReferencesStopThreads If true Tomcat attempts to terminate threads that have been started by the web application Stopping threads is performed via the deprecated for good reason Thread stop method and is likely to result in instability As such enabling this should be viewed as an option of last resort in a development environment and is not recommended in a production environment If not specified the default value of false will be used clearReferencesStopTimerThreads If true Tomcat attempts to terminate java util Timer threads that have been started by the web application Unlike standard threads timer threads can be stopped safely although there may still be side effects for the application If not specified the default value of false will be used processTlds Whether the context should process TLDs on startup The default is true The false setting is intended for special cases that know in advance TLDs are not part of the webapp renewThreadsWhenStoppingContext If true when this context is stopped Tomcat renews all the threads from the thread pool that was used to serve this context This also requires that the ThreadLocalLeakPreventionListener be configured in server xml and that the threadRenewalDelay property of the Executor be 0 If not specified the default value of true will be used unloadDelay Number of ms that the container will wait for servlets to unload If not specified the default value is 2000 ms unpackWAR If false the unpackWARs attribute of the owning Host will be overridden and the WAR file will not be unpacked If true the value of the owning Host s unpackWARs attribute will determine if the WAR is unpacked If not specified the default value is true Note that WAR files located outside of a Host s appBase are never unpacked useNaming Set to true the default to have Catalina enable a JNDI InitialContext for this web application that is compatible with Java2 Enterprise Edition J2EE platform conventions workDir Pathname to a scratch directory to be provided by this Context for temporary read write use by servlets within the associated web application This directory will be made visible to servlets in the web application by a servlet context attribute of type java io File named javax servlet context tempdir as described in the Servlet Specification If not specified a suitable directory underneath CATALINA BASE work will be provided Nested Components You can nest at most one instance of the following utility components by nesting a corresponding element inside your Context element Loader Configure the web application class loader that will be used to load servlet and bean classes for this web application Normally the default configuration of the class loader will be sufficient Manager Configure the session manager that will be used to create destroy and persist HTTP sessions for this web application Normally the default configuration of the session manager will be sufficient Realm Configure a realm that will allow its database of users and their associated roles to be utilized solely for this particular web application If not specified this web application will utilize the Realm associated with the owning Host or Engine Resources Configure the resource manager that will be used to access the static resources associated with this web application Normally the default configuration of the resource manager will be sufficient WatchedResource The auto deployer will monitor the specified static resource of the web application for updates and will reload the web application if is is updated The content of this element must be a string Special Features Logging A context is associated with the org apache catalina core ContainerBase enginename hostname path log category Note that the brackets are actually part of the name don t omit them Access Logs When you run a web server one of the output files normally generated is an access log which generates one line of information for each request processed by the server in a standard format Catalina includes an optional Valve implementation that can create access logs in the same standard format created by web servers or in any number of custom formats You can ask Catalina to create an access log for all requests processed by an Engine Host or Context by nesting a Valve element like this Context Valve className org apache catalina valves AccessLogValve prefix localhost access log suffix txt pattern common Context See Access Log Valve for more information on the configuration attributes that are supported Automatic Context Configuration If you use the standard Context implementation the following configuration steps occur automatically when Catalina is started or whenever this web application is reloaded No special configuration is required to enable this feature If you have not declared your own Loader element a standard web application class loader will be configured If you have not declared your own Manager element a standard session manager will be configured If you have not declared your own Resources element a standard resources manager will be configured The web application properties listed in conf web xml will be processed as defaults for this web application This is used to establish default mappings such as mapping the jsp extension to the corresponding JSP servlet and other standard features that apply to all web applications The web application properties listed in the WEB INF web xml resource

    Original URL path: http://ticket.eppa.es/docs/config/context.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Engine Container
    This name MUST match the name attributes of one of the Host elements nested immediately inside jvmRoute Identifier which must be used in load balancing scenarios to enable session affinity The identifier which must be unique across all Tomcat servers which participate in the cluster will be appended to the generated session identifier therefore allowing the front end proxy to always forward a particular session to the same Tomcat instance name Logical name of this Engine used in log and error messages When using multiple Service elements in the same Server each Engine MUST be assigned a unique name Standard Implementation The standard implementation of Engine is org apache catalina core StandardEngine It supports the following additional attributes in addition to the common attributes listed above Attribute Description Nested Components You can nest one or more Host elements inside this Engine element each representing a different virtual host associated with this server At least one Host is required and one of the nested Hosts MUST have a name that matches the name specified for the defaultHost attribute listed above You can nest at most one instance of the following utility components by nesting a corresponding element inside your Engine element Realm Configure a realm that will allow its database of users and their associated roles to be shared across all Hosts and Contexts nested inside this Engine unless overridden by a Realm configuration at a lower level Special Features Logging An engine is associated with the org apache catalina core ContainerBase enginename log category Note that the brackets are actually part of the name don t omit them Access Logs When you run a web server one of the output files normally generated is an access log which generates one line of information for each request processed by the server

    Original URL path: http://ticket.eppa.es/docs/config/engine.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Host Container
    own sub directory with temporary read write use Configuring a Context workDir will override use of the Host workDir configuration This directory will be made visible to servlets in the web application by a servlet context attribute of type java io File named javax servlet context tempdir as described in the Servlet Specification If not specified a suitable directory underneath CATALINA BASE work will be provided Nested Components You can nest one or more Context elements inside this Host element each representing a different web application associated with this virtual host You can nest at most one instance of the following utility components by nesting a corresponding element inside your Host element Realm Configure a realm that will allow its database of users and their associated roles to be shared across all Contexts nested inside this Host unless overridden by a Realm configuration at a lower level Special Features Logging A host is associated with the org apache catalina core ContainerBase engine name host name log category Note that the brackets are part of the name don t omit them Access Logs When you run a web server one of the output files normally generated is an access log which generates one line of information for each request processed by the server in a standard format Catalina includes an optional Valve implementation that can create access logs in the same standard format created by web servers or in any number of custom formats You can ask Catalina to create an access log for all requests processed by an Engine Host or Context by nesting a Valve element like this Host name localhost Valve className org apache catalina valves AccessLogValve prefix localhost access log suffix txt pattern common Host See Access Log Valve for more information on the configuration attributes that are supported Automatic Application Deployment If you are using the standard Host implementation the following actions take place automatically when Catalina is first started if the deployOnStartup property is set to true which is the default value Any XML file in the Host s xmlBase directory by default CATALINA BASE conf engine name host name is assumed to be a context XML descriptor containing a Context element and its associated sub elements for a single web application The web applications associated with each of these context XML descriptor files will be deployed first The docBase attribute of this Context element must only be set if the docBase is outside the Host s appBase For web applications located inside the Host s appBase the docBase will be the name of the XML file with xml replaced with war for a web application archive or the name of the XML file with xml removed for a directory The path attribute must not be set The context path used will be a slash character followed by the name of the XML file less the xml extension Multi level context paths may be defined using e g foo bar xml for a context path of foo bar The default web application that has a context path of may be defined by using a file called ROOT xml Any web application archive file within the Host s appBase directory that has not already been deployed as a result of a context XML descriptor does not have a corresponding directory of the same name without the war extension and is not excluded by deployIgnore will be deployed next The context path used will be a slash character followed by the web application archive name less the war extension The one exception to this rule is that a web application archive named ROOT war will be deployed with a context path of Multi level contexts may be defined by using e g use a WAR named foo bar war for a context path of foo bar If the unpackWARs attribute is true the web application archive file will be expanded to a directory of the same name without the war extension Note If you re deploy an updated WAR file while Tomcat is stopped be sure to delete the associated expanded directory before restarting Tomcat so that the updated WAR file will be re expanded when Tomcat restarts If copyXml is true it is false by default any web application archive file within the Hosts s appBase directory that does not have a corresponding context XML descriptor with a xml extension rather than a war extension in the Host s xmlBase will be scanned to see if it contains a context XML descriptor located at META INF context xml and if one is found the descriptor will be copied to the xmlBase directory and renamed Finally any sub directory within the Host s appBase that has not already been deployed as a result of a context XML descriptor and is not excluded by deployIgnore will be deployed The context path used will be a slash character followed by the directory name unless the directory name is ROOT in which case the context path will Multi level contexts may be defined by using e g use a directory named foo bar for a context path of foo bar If copyXml is true it is false by default any directory within the Hosts s appBase directory that does not have a corresponding context XML descriptor in the Host s xmlBase will be scanned to see if it contains a context XML descriptor located at META INF context xml and if one is found the descriptor will be copied to the xmlBase directory and renamed In addition to the automatic deployment that occurs at startup time you can also request that new XML configuration files WAR files or sub directories that are dropped in to the appBase or xmlBase in the case of an XML configuration file directory while Tomcat is running will be automatically deployed according to the rules described above The auto deployer will also track web applications for the following changes An update to the WEB INF

    Original URL path: http://ticket.eppa.es/docs/config/host.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Cluster object
    in this cluster implementation This manager configuration is identical to the one you would use in a regular Context configuration The default value is the org apache catalina ha session DeltaManager that is closely coupled with the SimpleTcpCluster implementation Other managers like the org apache catalina ha session BackupManager are could be loosely coupled and don t rely on the SimpleTcpCluster for its data replication Channel The Channel and its sub components are all part of the IO layer for the cluster group and is a module in it s own that we have nick named Tribes Any configuring and tuning of the network layer the messaging and the membership logic will be done in the channel and its nested components You can always find out more about Apache Tribes Valve The Tomcat Cluster implementation uses Tomcat Valves to track when requests enter and exit the servlet container It uses these valves to be able to make intelligent decisions on when to replicate data which is always at the end of a request Deployer The Deployer component is the Tomcat Farm Deployer It allows you to deploy and undeploy applications cluster wide ClusterListener ClusterListener s are used to track messages sent and received using the SimpleTcpCluster If you wish to track messages you can add a listener here or you can add a valve to the channel object Deprecated configuration options Deprecated settings In the previous version of Tomcat you were able to control session manager settings using manager property value This has been discontinued as the way it was written interferes with the ability to support multiple different manager classes under one cluster implementation as the same properties might have the different effect on different managers Attributes SimpleTcpCluster Attributes Attribute Description className The main cluster class currently only one

    Original URL path: http://ticket.eppa.es/docs/config/cluster.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - Container Provided Filters
    the same images i e the images will be accessed repeatedly within a relatively short timespan Note When the content type includes a charset e g ExpiresByType text xml charset utf 8 Tomcat removes blank chars between the and the charset keyword Due to this configuration of an expiration with a charset must not include such a space character Sample init param param name ExpiresByType text html param name param value access plus 1 month 15 days 2 hours param value init param init param 2592000 seconds 30 days param name ExpiresByType image gif param name param value A2592000 param value init param It overrides for the specified MIME type only any expiration date set by the ExpiresDefault directive You can also specify the expiration time calculation using an alternate syntax described earlier in this document ExpiresDefault This directive sets the default algorithm for calculating the expiration time for all documents in the affected realm It can be overridden on a type by type basis by the ExpiresByType directive See the description of that directive for details about the syntax of the argument and the alternate syntax description as well Troubleshooting To troubleshoot enable logging on the org apache catalina filters ExpiresFilter Extract of logging properties org apache catalina filters ExpiresFilter level FINE Sample of initialization log message Mar 26 2010 2 01 41 PM org apache catalina filters ExpiresFilter init FINE Filter initialized with configuration ExpiresFilter excludedResponseStatusCode 304 default null byType image ExpiresConfiguration startingPoint ACCESS TIME duration 10 MINUTE text css ExpiresConfiguration startingPoint ACCESS TIME duration 10 MINUTE text javascript ExpiresConfiguration startingPoint ACCESS TIME duration 10 MINUTE Sample of per request log message where ExpiresFilter adds an expiration date Mar 26 2010 2 09 47 PM org apache catalina filters ExpiresFilter onBeforeWriteResponseBody FINE Request tomcat gif with response status 200 content type image gif set expiration date 3 26 10 2 19 PM Sample of per request log message where ExpiresFilter does not add an expiration date Mar 26 2010 2 10 27 PM org apache catalina filters ExpiresFilter onBeforeWriteResponseBody FINE Request docs config manager html with response status 200 content type text html no expiration configured Remote Address Filter Introduction The Remote Address Filter allows you to compare the IP address of the client that submitted this request against one or more regular expressions and either allow the request to continue or refuse to process the request from this client The syntax for regular expressions is different than that for standard wildcard matching Tomcat uses the java util regex package Please consult the Java documentation for details of the expressions supported Note There is a caveat when using this filter with IPv6 addresses Format of the IP address that this valve is processing depends on the API that was used to obtain it If the address was obtained from Java socket using Inet6Address class its format will be x x x x x x x x That is the IP address for localhost will be 0 0 0 0 0 0 0 1 instead of the more widely used 1 Consult your access logs for the actual value See also Remote Host Filter Filter Class Name The filter class name for the Remote Address Filter is org apache catalina filters RemoteAddrFilter Initialisation parameters The Remote Address Filter supports the following initialisation parameters Attribute Description allow A regular expression using java util regex that the remote client s IP address is compared to If this attribute is specified the remote address MUST match for this request to be accepted If this attribute is not specified all requests will be accepted UNLESS the remote address matches a deny pattern deny A regular expression using java util regex that the remote client s IP address is compared to If this attribute is specified the remote address MUST NOT match for this request to be accepted If this attribute is not specified request acceptance is governed solely by the accept attribute Example To allow access only for the clients connecting from localhost filter filter name Remote Address Filter filter name filter class org apache catalina filters RemoteAddrFilter filter class init param param name allow param name param value 127 d d d 1 0 0 0 0 0 0 0 1 param value init param filter filter mapping filter name Remote Address Filter filter name url pattern url pattern filter mapping Remote Host Filter Introduction The Remote Host Filter allows you to compare the hostname of the client that submitted this request against one or more regular expressions and either allow the request to continue or refuse to process the request from this client The syntax for regular expressions is different than that for standard wildcard matching Tomcat uses the java util regex package Please consult the Java documentation for details of the expressions supported See also Remote Address Filter Filter Class Name The filter class name for the Remote Address Filter is org apache catalina filters RemoteHostFilter Initialisation parameters The Remote Host Filter supports the following initialisation parameters Attribute Description allow A regular expression using java util regex that the remote client s hostname is compared to If this attribute is specified the remote hostname MUST match for this request to be accepted If this attribute is not specified all requests will be accepted UNLESS the remote hostname matches a deny pattern deny A regular expression using java util regex that the remote client s hostname is compared to If this attribute is specified the remote hostname MUST NOT match for this request to be accepted If this attribute is not specified request acceptance is governed solely by the accept attribute Remote IP Filter Introduction Tomcat port of mod remoteip this filter replaces the apparent client remote IP address and hostname for the request with the IP address list presented by a proxy or a load balancer via a request headers e g X Forwarded For Another feature of this filter is to replace the apparent scheme http https server port

    Original URL path: http://ticket.eppa.es/docs/config/filter.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The GlobalNamingResources Component
    context override Set this to false if you do not want an env entry for the same environment entry name found in the web application deployment descriptor to override the value specified here By default overrides are allowed type The fully qualified Java class name expected by the web application for this environment entry Must be one of the legal values for env entry type in the web application deployment descriptor java lang Boolean java lang Byte java lang Character java lang Double java lang Float java lang Integer java lang Long java lang Short or java lang String value The parameter value that will be presented to the application when requested from the JNDI context This value must be convertable to the Java type defined by the type attribute Resource Definitions You can declare the characteristics of resources to be returned for JNDI lookups of resource ref and resource env ref elements in the web application deployment descriptor by defining them in this element and then linking them with ResourceLink elements in the Context element You MUST also define any other needed parameters using attributes on the Resource element to configure the object factory to be used if not known to Tomcat already and the properties used to configure that object factory For example you can create a resource definition like this GlobalNamingResources Resource name jdbc EmployeeDB auth Container type javax sql DataSource description Employees Database for HR Applications GlobalNamingResources This is equivalent to the inclusion of the following element in the web application deployment descriptor WEB INF web xml resource ref description Employees Database for HR Applications description res ref name jdbc EmployeeDB res ref name res ref type javax sql DataSource res ref type res auth Container res auth resource ref but does not require modification of

    Original URL path: http://ticket.eppa.es/docs/config/globalresources.html (2015-09-25)
    Open archived version from archive

  • Apache Tomcat 7 Configuration Reference (7.0.22) - The Jar Scanner Component
    Implementation Nested Components Special Features Introduction The Jar Scanner element represents the component that is used to scan the web application for JAR files It is typically used during web application start to identify configuration files such as TLDs or web fragment xml files that must be processed as part of the web application initialisation A Jar Scanner element MAY be nested inside a Context component If it is not included a default Jar Scanner configuration will be created automatically which is sufficient for most requirements Attributes Common Attributes All implementations of Jar Scanner support the following attributes Attribute Description className Java class name of the implementation to use This class must implement the org apache tomcat JarScanner interface If not specified the standard value defined below will be used Standard Implementation The standard implementation of Jar Scanner is org apache tomcat util scan StandardJarScanner It supports the following additional attributes in addition to the common attributes listed above Attribute Description scanClassPath If true the full web application classpath including the shared and common classloaders will be scanned for Jar files in addition to the web application The default is true scanAllFiles If true any files found on the classpath

    Original URL path: http://ticket.eppa.es/docs/config/jar-scanner.html (2015-09-25)
    Open archived version from archive