Jetty is a project at the Eclipse Foundation.
| Homepage: | http://www.eclipse.org/jetty |
| Downloads: | http://download.eclipse.org/jetty/ |
| Documentation: | http://www.eclipse.org/jetty/documentation/current/ |
| About: | http://www.eclipse.org/jetty/about.php |
| Jetty Powered: | http://www.eclipse.org/jetty/powered/ |
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
Securing Jetty
Securing against accidental or malicious termination
You can start Jetty in such a way as to require identification before a termination request is accepted. This can help safeguard against either accidental or malicious terminations.
This involves starting jetty with a STOP.PORT parameter:
The STOP.PORT is the number of a port on which Jetty will listen for termination requests. In this case, the port number is 8079. You can then stop jetty either with a cntrl-c in the controlling terminal window (unless you have disassociated the Jetty process from a terminal), or by supplying this port number on a stop request from any terminal.
You can also supply a secret key on startup which must also be present on the termination request to enhance security:
As a further security measure, you can omit the STOP.KEY property on startup, in which case Jetty will generate and print on stdout a random key:
This key should then be supplied on the termination request: