2019-11-08 17:42:53 +00:00
|
|
|
<?xml version="1.0" encoding="UTF-8" ?>
|
2012-11-22 21:42:15 +00:00
|
|
|
<!DOCTYPE Configure PUBLIC "-//Jetty//Configure//EN" "http://www.eclipse.org/jetty/configure.dtd">
|
2011-12-23 00:56:48 +00:00
|
|
|
|
2017-03-10 18:48:48 +00:00
|
|
|
<!-- This configuration supports Jetty 9. Do not remove this line. -->
|
|
|
|
|
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- ========================================================================= -->
|
|
|
|
|
<!-- This file configures the Jetty server. -->
|
|
|
|
|
<!-- All changes require a restart of I2P. -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- Commonly changed settings: -->
|
|
|
|
|
<!-- * host: Change 127.0.0.1 to 0.0.0.0 in the addListener section -->
|
|
|
|
|
<!-- to access the server directly (bypassing i2p) -->
|
2012-03-11 16:46:45 +00:00
|
|
|
<!-- from other computers. -->
|
2012-03-10 21:54:55 +00:00
|
|
|
<!-- * port: Default 7658 in the addConnector section -->
|
|
|
|
|
<!-- * docroot: Change the ResourceBase in the contexts/base-context.xml file -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- to serve files from a different location. -->
|
2017-03-01 16:42:57 +00:00
|
|
|
<!-- * threads: Raise maxThreads in the ThreadPool section -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- if you have a high-traffic site and get a lot of warnings. -->
|
|
|
|
|
<!-- * Uncomment the addWebApplications section to use to enable -->
|
|
|
|
|
<!-- war files placed in the webapps/ dir. -->
|
|
|
|
|
<!-- * Uncomment the line to allow Jetty to follow symlinks -->
|
|
|
|
|
<!-- -->
|
2017-03-01 16:42:57 +00:00
|
|
|
<!-- I2P uses Jetty 9. If you need web server features not found -->
|
|
|
|
|
<!-- in Jetty 9, you may install and run Jetty 7 or 8 in a different JVM -->
|
2012-03-06 19:25:03 +00:00
|
|
|
<!-- or run any other web server such as Apache. If you do run another web -->
|
2017-03-01 16:42:57 +00:00
|
|
|
<!-- server instead, be sure and disable the Jetty 9 server for your -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- eepsite on http://127.0.0.1:7657/configclients.jsp . -->
|
|
|
|
|
<!-- -->
|
2012-03-10 21:54:55 +00:00
|
|
|
<!-- Jetty now uses the I2P logging system rather than wrapper.log. -->
|
2013-04-14 14:02:43 +00:00
|
|
|
<!-- Use the log override org.eclipse.jetty.server.Server to adjust the log level. -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- -->
|
|
|
|
|
<!-- Note that the XML encoding for this file is UTF-8. -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- If you have a 'split' directory installation, with configuration -->
|
2019-11-08 17:42:53 +00:00
|
|
|
<!-- files in ~/.i2p (Linux), %LOCALAPPDATA%\I2P (Windows), -->
|
2016-05-19 19:03:53 +00:00
|
|
|
<!-- or /Users/(user)/Library/Application Support/i2p (Mac), be sure to -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- edit the file in the configuration directory, NOT the install directory. -->
|
2014-11-28 14:23:34 +00:00
|
|
|
<!-- When running as a Linux daemon, the configuration directory is -->
|
|
|
|
|
<!-- /var/lib/i2p and the install directory is /usr/share/i2p . -->
|
2016-05-19 19:03:53 +00:00
|
|
|
<!-- When running as a Windows service, -->
|
|
|
|
|
<!-- the configuration directory is \ProgramData\i2p -->
|
|
|
|
|
<!-- and the install directory is \Program Files\i2p . -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- -->
|
|
|
|
|
<!-- ========================================================================= -->
|
|
|
|
|
|
2017-03-01 16:42:57 +00:00
|
|
|
<!-- ========================================================================= -->
|
|
|
|
|
<!-- Configure the Jetty Server -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- Documentation of this file format can be found at: -->
|
|
|
|
|
<!-- http://www.eclipse.org/jetty/documentation/current/jetty-xml-config.html -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- ========================================================================= -->
|
2011-12-23 00:56:48 +00:00
|
|
|
|
|
|
|
|
|
2012-11-22 21:17:50 +00:00
|
|
|
<Configure id="Server" class="org.eclipse.jetty.server.Server">
|
2011-12-23 00:56:48 +00:00
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Server Thread Pool -->
|
|
|
|
|
<!-- =========================================================== -->
|
2017-03-01 16:42:57 +00:00
|
|
|
<Arg>
|
2011-12-23 00:56:48 +00:00
|
|
|
|
2011-12-24 17:09:01 +00:00
|
|
|
<!-- PICK ONE -->
|
|
|
|
|
|
Console and Eepsite Jetty:
Switch back to QueuedThreadPool (ticket #1395)
In Jetty 5/6, the default QTP was not concurrent, so we switched to
ThreadPoolExecutor with a fixed-size queue, a set maxThreads,
and a RejectedExecutionPolicy of CallerRuns.
Unfortunately, CallerRuns causes lockups in Jetty NIO.
In addition, no flavor of TPE gives us what QTP does:
- TPE direct handoff (which we were using) never queues.
This doesn't provide any burst management when maxThreads is reached.
CallerRuns was an attempt to work around that.
- TPE unbounded queue does not adjust the number of threads.
This doesn't provide automatic resource management.
- TPE bounded queue does not add threads until the queue is full.
This doesn't provide good responsiveness to even small bursts.
QTP adds threads as soon as the queue is non-empty.
QTP as of Jetty 7 uses concurrent.
QTP unbounded queue is the default in Jetty.
So switch back to QTP with a bounded queue, which does what we want,
which is first expand the thread pool, then start queueing, then reject.
ref:
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html
https://wiki.eclipse.org/Jetty/Howto/High_Load
2014-10-20 14:01:36 +00:00
|
|
|
<!--
|
|
|
|
|
Recommended.
|
|
|
|
|
Two threads are used for the Connector and Acceptor.
|
|
|
|
|
Concurrent requests above maxThreads + queue size - 2 will be rejected and logged.
|
|
|
|
|
Due to the way QTP works, queue size should be larger than maxThreads.
|
|
|
|
|
Increase all values for high-traffic eepsites.
|
|
|
|
|
|
|
|
|
|
ref:
|
|
|
|
|
https://wiki.eclipse.org/Jetty/Howto/High_Load
|
|
|
|
|
http://trac.i2p2.i2p/ticket/1395
|
2011-12-24 17:09:01 +00:00
|
|
|
-->
|
2012-11-22 21:17:50 +00:00
|
|
|
<New class="org.eclipse.jetty.util.thread.QueuedThreadPool">
|
2017-03-01 16:42:57 +00:00
|
|
|
<Arg type="int">20</Arg> <!-- maxThreads, overridden below -->
|
|
|
|
|
<Arg type="int">3</Arg> <!-- minThreads, overridden below -->
|
|
|
|
|
<Arg type="int">60000</Arg> <!-- maxIdleTimeMs, overridden below -->
|
Console and Eepsite Jetty:
Switch back to QueuedThreadPool (ticket #1395)
In Jetty 5/6, the default QTP was not concurrent, so we switched to
ThreadPoolExecutor with a fixed-size queue, a set maxThreads,
and a RejectedExecutionPolicy of CallerRuns.
Unfortunately, CallerRuns causes lockups in Jetty NIO.
In addition, no flavor of TPE gives us what QTP does:
- TPE direct handoff (which we were using) never queues.
This doesn't provide any burst management when maxThreads is reached.
CallerRuns was an attempt to work around that.
- TPE unbounded queue does not adjust the number of threads.
This doesn't provide automatic resource management.
- TPE bounded queue does not add threads until the queue is full.
This doesn't provide good responsiveness to even small bursts.
QTP adds threads as soon as the queue is non-empty.
QTP as of Jetty 7 uses concurrent.
QTP unbounded queue is the default in Jetty.
So switch back to QTP with a bounded queue, which does what we want,
which is first expand the thread pool, then start queueing, then reject.
ref:
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html
https://wiki.eclipse.org/Jetty/Howto/High_Load
2014-10-20 14:01:36 +00:00
|
|
|
<Arg>
|
|
|
|
|
<New class="java.util.concurrent.LinkedBlockingQueue">
|
|
|
|
|
<Arg type="int">40</Arg>
|
|
|
|
|
</New>
|
|
|
|
|
</Arg>
|
|
|
|
|
<Set name="minThreads">3</Set>
|
|
|
|
|
<Set name="maxThreads">20</Set>
|
2017-03-01 16:42:57 +00:00
|
|
|
<Set name="idleTimeout">60000</Set>
|
Console and Eepsite Jetty:
Switch back to QueuedThreadPool (ticket #1395)
In Jetty 5/6, the default QTP was not concurrent, so we switched to
ThreadPoolExecutor with a fixed-size queue, a set maxThreads,
and a RejectedExecutionPolicy of CallerRuns.
Unfortunately, CallerRuns causes lockups in Jetty NIO.
In addition, no flavor of TPE gives us what QTP does:
- TPE direct handoff (which we were using) never queues.
This doesn't provide any burst management when maxThreads is reached.
CallerRuns was an attempt to work around that.
- TPE unbounded queue does not adjust the number of threads.
This doesn't provide automatic resource management.
- TPE bounded queue does not add threads until the queue is full.
This doesn't provide good responsiveness to even small bursts.
QTP adds threads as soon as the queue is non-empty.
QTP as of Jetty 7 uses concurrent.
QTP unbounded queue is the default in Jetty.
So switch back to QTP with a bounded queue, which does what we want,
which is first expand the thread pool, then start queueing, then reject.
ref:
http://docs.oracle.com/javase/6/docs/api/java/util/concurrent/ThreadPoolExecutor.html
https://wiki.eclipse.org/Jetty/Howto/High_Load
2014-10-20 14:01:36 +00:00
|
|
|
<Set name="daemon">true</Set>
|
|
|
|
|
<Set name="name">Eepsite Jetty</Set>
|
2011-12-23 00:56:48 +00:00
|
|
|
</New>
|
2017-03-01 16:42:57 +00:00
|
|
|
</Arg>
|
2011-12-23 00:56:48 +00:00
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Set connectors -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- One of each type! -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
|
|
|
|
|
<!-- Use this connector for many frequently idle connections
|
|
|
|
|
and for threadless continuations.
|
2012-10-14 13:54:08 +00:00
|
|
|
Not recommended on Java 5 - comment this out, and uncomment the
|
|
|
|
|
SocketConnector below.
|
|
|
|
|
Do not use for gij or JamVM - comment this out, and uncomment the
|
2012-09-25 19:21:28 +00:00
|
|
|
SocketConnector below.
|
2019-11-08 17:42:53 +00:00
|
|
|
-->
|
2011-12-23 00:56:48 +00:00
|
|
|
<Call name="addConnector">
|
|
|
|
|
<Arg>
|
2017-03-01 16:42:57 +00:00
|
|
|
<New class="org.eclipse.jetty.server.ServerConnector">
|
|
|
|
|
<Arg><Ref id="Server" /></Arg>
|
|
|
|
|
<Arg type="int">1</Arg> <!-- number of acceptors -->
|
|
|
|
|
<Arg type="int">0</Arg> <!-- default number of selectors -->
|
|
|
|
|
<Arg>
|
|
|
|
|
<Array type="org.eclipse.jetty.server.ConnectionFactory"> <!-- varargs so we need an array -->
|
|
|
|
|
<Item>
|
|
|
|
|
<New class="org.eclipse.jetty.server.HttpConnectionFactory">
|
|
|
|
|
<Arg>
|
|
|
|
|
<New class="org.eclipse.jetty.server.HttpConfiguration">
|
|
|
|
|
<Set name="sendServerVersion">false</Set>
|
2018-03-10 16:56:59 +00:00
|
|
|
<Set name="sendDateHeader">false</Set>
|
|
|
|
|
<Set name="sendXPoweredBy">false</Set>
|
2017-03-01 16:42:57 +00:00
|
|
|
</New>
|
|
|
|
|
</Arg>
|
|
|
|
|
</New>
|
|
|
|
|
</Item>
|
|
|
|
|
</Array>
|
|
|
|
|
</Arg>
|
2012-09-25 19:21:28 +00:00
|
|
|
<Set name="host">127.0.0.1</Set>
|
|
|
|
|
<Set name="port">7658</Set>
|
2017-03-01 16:42:57 +00:00
|
|
|
<Set name="idleTimeout">600000</Set>
|
2012-09-25 19:21:28 +00:00
|
|
|
</New>
|
|
|
|
|
</Arg>
|
|
|
|
|
</Call>
|
|
|
|
|
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
|
|
|
|
|
<!-- To add a HTTPS SSL listener -->
|
|
|
|
|
<!-- see jetty-ssl.xml to add an ssl connector. use -->
|
2011-12-24 17:09:01 +00:00
|
|
|
<!-- To enable this change clients.config args to be: -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- clientApp3.args=etc/jetty.xml etc/jetty-ssl.xml -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
|
|
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Set up global session ID manager -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!--
|
|
|
|
|
<Set name="sessionIdManager">
|
2012-11-22 21:17:50 +00:00
|
|
|
<New class="org.eclipse.jetty.server.session.HashSessionIdManager">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Set name="workerName">node1</Set>
|
|
|
|
|
</New>
|
|
|
|
|
</Set>
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
2019-11-08 17:42:53 +00:00
|
|
|
<!-- Set handler Collection Structure -->
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<Set name="handler">
|
2012-11-22 21:17:50 +00:00
|
|
|
<New id="Handlers" class="org.eclipse.jetty.server.handler.HandlerCollection">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Set name="handlers">
|
2012-11-22 21:17:50 +00:00
|
|
|
<Array type="org.eclipse.jetty.server.Handler">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Item>
|
2012-11-22 21:17:50 +00:00
|
|
|
<New id="Contexts" class="org.eclipse.jetty.server.handler.ContextHandlerCollection"/>
|
2011-12-23 00:56:48 +00:00
|
|
|
</Item>
|
|
|
|
|
<Item>
|
2012-11-22 21:17:50 +00:00
|
|
|
<New id="DefaultHandler" class="org.eclipse.jetty.server.handler.DefaultHandler"/>
|
2011-12-23 00:56:48 +00:00
|
|
|
</Item>
|
|
|
|
|
<Item>
|
2012-11-22 21:17:50 +00:00
|
|
|
<New id="RequestLog" class="org.eclipse.jetty.server.handler.RequestLogHandler"/>
|
2011-12-23 00:56:48 +00:00
|
|
|
</Item>
|
|
|
|
|
</Array>
|
|
|
|
|
</Set>
|
|
|
|
|
</New>
|
|
|
|
|
</Set>
|
2012-11-22 21:17:50 +00:00
|
|
|
|
|
|
|
|
<!-- =============================================================== -->
|
|
|
|
|
<!-- Create the deployment manager -->
|
|
|
|
|
<!-- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -->
|
|
|
|
|
<!-- The deplyment manager handles the lifecycle of deploying web -->
|
|
|
|
|
<!-- applications. Apps are provided by instances of the -->
|
|
|
|
|
<!-- AppProvider interface. Typically these are provided by -->
|
|
|
|
|
<!-- one or more of: -->
|
|
|
|
|
<!-- jetty-webapps.xml - monitors webapps for wars and dirs -->
|
|
|
|
|
<!-- jetty-contexts.xml - monitors contexts for context xml -->
|
|
|
|
|
<!-- jetty-templates.xml - monitors contexts and templates -->
|
|
|
|
|
<!-- =============================================================== -->
|
|
|
|
|
<Call name="addBean">
|
|
|
|
|
<Arg>
|
|
|
|
|
<New id="DeploymentManager" class="org.eclipse.jetty.deploy.DeploymentManager">
|
|
|
|
|
<Set name="contexts">
|
|
|
|
|
<Ref id="Contexts" />
|
|
|
|
|
</Set>
|
|
|
|
|
<Call name="setContextAttribute">
|
|
|
|
|
<Arg>org.eclipse.jetty.server.webapp.ContainerIncludeJarPattern</Arg>
|
|
|
|
|
<Arg>.*/.*jsp-api-[^/]*\.jar$|.*/.*jsp-[^/]*\.jar$|.*/.*taglibs[^/]*\.jar$</Arg>
|
|
|
|
|
</Call>
|
|
|
|
|
</New>
|
|
|
|
|
</Arg>
|
|
|
|
|
</Call>
|
|
|
|
|
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Configure the context deployer -->
|
|
|
|
|
<!-- A context deployer will deploy contexts described in -->
|
|
|
|
|
<!-- configuration files discovered in a directory. -->
|
|
|
|
|
<!-- The configuration directory can be scanned for hot -->
|
|
|
|
|
<!-- deployments at the configured scanInterval. -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- This deployer is configured to deploy contexts configured -->
|
|
|
|
|
<!-- in the $JETTY_HOME/contexts directory -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- =========================================================== -->
|
2012-11-22 21:17:50 +00:00
|
|
|
<Ref id="DeploymentManager">
|
|
|
|
|
<Call name="addAppProvider">
|
|
|
|
|
<Arg>
|
2017-03-01 16:42:57 +00:00
|
|
|
<New class="org.eclipse.jetty.deploy.providers.WebAppProvider">
|
2012-11-22 21:17:50 +00:00
|
|
|
<Set name="monitoredDirName">./eepsite/contexts</Set>
|
2013-04-08 15:29:02 +00:00
|
|
|
<Set name="scanInterval">120</Set>
|
2012-11-22 21:17:50 +00:00
|
|
|
</New>
|
|
|
|
|
</Arg>
|
|
|
|
|
</Call>
|
|
|
|
|
</Ref>
|
2011-12-23 00:56:48 +00:00
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Configure the webapp deployer. -->
|
|
|
|
|
<!-- A webapp deployer will deploy standard webapps discovered -->
|
|
|
|
|
<!-- in a directory at startup, without the need for additional -->
|
|
|
|
|
<!-- configuration files. It does not support hot deploy or -->
|
|
|
|
|
<!-- non standard contexts (see ContextDeployer above). -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- This deployer is configured to deploy webapps from the -->
|
|
|
|
|
<!-- $JETTY_HOME/webapps directory -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- Normally only one type of deployer need be used. -->
|
|
|
|
|
<!-- -->
|
|
|
|
|
<!-- =========================================================== -->
|
2012-11-22 21:17:50 +00:00
|
|
|
<Ref id="DeploymentManager">
|
|
|
|
|
<Call id="webappprovider" name="addAppProvider">
|
2013-04-08 15:29:02 +00:00
|
|
|
<Arg>
|
2019-05-12 18:14:55 +00:00
|
|
|
<New id="WebAppProvider" class="org.eclipse.jetty.deploy.providers.WebAppProvider">
|
2013-04-08 15:29:02 +00:00
|
|
|
<Set name="monitoredDirName">./eepsite/webapps</Set>
|
|
|
|
|
<Set name="parentLoaderPriority">false</Set>
|
2019-05-12 18:14:55 +00:00
|
|
|
<!-- this is required because Jetty can't handle jars inside wars,
|
|
|
|
|
for example in php-java-bridge's JavaBridgeTemplate.war
|
|
|
|
|
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=433708
|
|
|
|
|
See our ticket 2477
|
|
|
|
|
-->
|
|
|
|
|
<Set name="extractWars">true</Set>
|
2013-04-08 15:29:02 +00:00
|
|
|
<Set name="defaultsDescriptor">./eepsite/etc/webdefault.xml</Set>
|
|
|
|
|
</New>
|
|
|
|
|
</Arg>
|
2012-11-22 21:17:50 +00:00
|
|
|
</Call>
|
|
|
|
|
</Ref>
|
|
|
|
|
|
2019-05-12 18:14:55 +00:00
|
|
|
<!-- Fixup for webapps to work, see our ticket 2477
|
|
|
|
|
Note that for webapps with uncompiled jsps, you will also
|
|
|
|
|
need a java compiler in the classpath;
|
|
|
|
|
The easiest way (Debian/Ubuntu) is to put a symlink in $I2P/lib:
|
|
|
|
|
sudo apt install libecj-java
|
|
|
|
|
cd $I2P/lib
|
|
|
|
|
ln -s /usr/share/java/ecj.jar
|
|
|
|
|
stop and then start i2p (restart alone will not pick up the new jar in the classpath)
|
|
|
|
|
-->
|
|
|
|
|
<Call class="net.i2p.servlet.WebAppProviderConfiguration" name="configure">
|
|
|
|
|
<Arg><Ref refid="WebAppProvider"/></Arg>
|
|
|
|
|
</Call>
|
|
|
|
|
|
2016-03-15 14:08:28 +00:00
|
|
|
<!-- ===================== -->
|
|
|
|
|
<!-- DefaultHandler config -->
|
|
|
|
|
<!-- http://stackoverflow.com/questions/4202275/how-to-prevent-jetty-from-showing-context-related-information -->
|
|
|
|
|
<!-- ===================== -->
|
|
|
|
|
<Ref id="DefaultHandler">
|
|
|
|
|
<Set name="showContexts">false</Set>
|
|
|
|
|
</Ref>
|
|
|
|
|
|
2011-12-23 00:56:48 +00:00
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Configure Authentication Realms -->
|
|
|
|
|
<!-- Realms may be configured for the entire server here, or -->
|
|
|
|
|
<!-- they can be configured for a specific web app in a context -->
|
|
|
|
|
<!-- configuration (see $(jetty.home)/contexts/test.xml for an -->
|
|
|
|
|
<!-- example). -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- UNCOMMENT TO ACTIVATE
|
|
|
|
|
<Set name="UserRealms">
|
2012-11-22 21:17:50 +00:00
|
|
|
<Array type="org.eclipse.jetty.security.LoginService">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Item>
|
2012-11-22 21:17:50 +00:00
|
|
|
<New class="org.eclipse.jetty.security.HashLoginService">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Set name="name">Test Realm</Set>
|
|
|
|
|
<Set name="config">./eepsite/etc/realm.properties</Set>
|
|
|
|
|
<Set name="refreshInterval">0</Set>
|
|
|
|
|
</New>
|
|
|
|
|
</Item>
|
|
|
|
|
</Array>
|
|
|
|
|
</Set>
|
|
|
|
|
-->
|
|
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- Configure Request Log -->
|
|
|
|
|
<!-- Request logs may be configured for the entire server here, -->
|
|
|
|
|
<!-- or they can be configured for a specific web app in a -->
|
|
|
|
|
<!-- contexts configuration (see $(jetty.home)/contexts/test.xml -->
|
|
|
|
|
<!-- for an example). -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<Ref id="RequestLog">
|
|
|
|
|
<Set name="requestLog">
|
2011-12-29 23:25:27 +00:00
|
|
|
<New id="RequestLogImpl" class="net.i2p.jetty.I2PRequestLog">
|
2011-12-23 00:56:48 +00:00
|
|
|
<Set name="filename">./eepsite/logs/yyyy_mm_dd.request.log</Set>
|
|
|
|
|
<Set name="filenameDateFormat">yyyy_MM_dd</Set>
|
|
|
|
|
<Set name="retainDays">90</Set>
|
|
|
|
|
<Set name="append">true</Set>
|
|
|
|
|
<Set name="extended">false</Set>
|
|
|
|
|
<Set name="logCookies">false</Set>
|
|
|
|
|
<Set name="LogTimeZone">GMT</Set>
|
2016-01-06 17:45:35 +00:00
|
|
|
<!-- False for b32 logging. True for b64 logging. Default false -->
|
|
|
|
|
<Set name="b64">false</Set>
|
2011-12-23 00:56:48 +00:00
|
|
|
</New>
|
|
|
|
|
</Set>
|
|
|
|
|
</Ref>
|
|
|
|
|
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<!-- extra options -->
|
|
|
|
|
<!-- =========================================================== -->
|
|
|
|
|
<Set name="stopAtShutdown">true</Set>
|
2017-03-01 16:42:57 +00:00
|
|
|
<Set name="stopTimeout">1000</Set>
|
2011-12-23 00:56:48 +00:00
|
|
|
|
|
|
|
|
</Configure>
|
