private support for your internal/customer projects ... custom extensions and distributions ... versioned snapshots for indefinite support ... scalability guidance for your apps and Ajax/Comet projects ... development services from 1 day to full product delivery
Request logs are a record of the requests that the server has processed. There is one entry per request received, and commonly in the standard NCSA format, so you can use tools like Webalizer to analyze them conveniently.
A standard request log entry includes the client IP address, date, method, URL, result, size, referrer, and user agent, for example:
126.96.36.199 - - [27/Aug/2004:10:16:17 +0000] "GET /jetty/tut/XmlConfiguration.html HTTP/1.1" 200 76793 "http://localhost:8080/jetty/tut/logging.html" "Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040614 Firefox/0.8"
Jetty provides an implementation called
NCSARequestLog which supports the NCSA format in
files that you can roll over on a daily basis.
If neither of these options meets your needs, you can implement a
custom request logger by implementing Jetty's
interface and plugging it in similar to the NCSARequestLog, as shown
To configure a single request log for the entire Jetty Server instance:
The equivalent code is:
This configures a request log in
$JETTY_HOME/logs with filenames including the date.
Old log files are kept for 90 days before being deleted. Existing log
files are appended to and the extended NCSA format is used in the GMT
To examine many more configuration options, see NCSARequestLog.java