Options for configuring Jetty.
Options for configuring Jetty.
If true, calls join() on Server instance (blocking till server shuts down)
The network interface connectors will bind to. If None or 0.0.0.0, binds to all interfaces.
A ServerConnector will be created listening on this port.
Max threads in the threadpool used by connectors to run (eventually) the handler.
Minimum threads to keep alive in the Jetty threadpool.
If true, all threads in Jetty's threadpool will be daemon threads.
A function to mess around with the Server instance before start is called.
The max idle time for a connection (roughly Socket.setSoTimeout(int))
If true an HTTP connector is setup listening on port
If true an SSL connector is setup listing on sslPort
The port to listen for SSL connections if enableSsl
is true.
If true, include date in HTTP headers
The size of the buffer into which the response is aggregated before being sent to the client. Larger buffer is less likely to block content producer, but could increase from client's perspective.
Max size of a request header. Larger sizes allow for more cookies or stuff encoded in a URL.
Max size of a response header. Similar use cases as requestHeaderSize
.
If true, send the Server header in responses.
Specifies the keystore (private certs) to use for SSL connections
Password for keystore
Specifies the keystore (public certs) to use for SSL connections
Password for trustStore
Policy for client SSL authentication (i.e. Need/Want).
Cipher suites to exclude when using SSL
Protocols to exclude when using SSL
Basic request.
Basic request. Modeled after Request Map in https://github.com/ring-clojure/ring/blob/master/SPEC
The port on which the request is being handled.
The resolved server name, or the server IP address.
The IP address of the client or the last proxy that sent the request.
The request URI, excluding the query string and the "?" separator. Must start with "/".
The query string, if present.
The transport protocol.
The transport protocol.
The protocol the request was made with, e.g. "HTTP/1.1"
The SSL client certificate, if supplied.
A map of lowercased header names to corresponding values.
The request body, if present.
Other info tacked on to the request.
Basic response.
Basic response. Modeled after Response Map in https://github.com/ring-clojure/ring/blob/master/SPEC
The HTTP status code, must be greater than or equal to 100.
A map of HTTP header names to header values. These values may be either Strings, in which case one name/value header will be sent in the HTTP response, or a seq of Strings, in which case a name/value header will be sent for each such String value.
A representation of the response body, if a response body is appropriate for the response's status code.
Extra key/value data attached the the response.
Do a thing with guaranteed cleanup: http://stackoverflow.com/a/8865994/69689 aka Using aka ARM aka try-with-resource
Helper regexs for parsing HTTP.
Helper regexs for parsing HTTP. see https://github.com/ring-clojure/ring/blob/01de0cf1bbab402905bc65789bebb9a7dc36d974/ring-core/src/ring/util/parsing.clj
Functionality for running handlers on Jetty.
Functionality for running handlers on Jetty. Largely a port of https://github.com/ring-clojure/ring/blob/4a3584570ad9e7b17f6b1c8a2a17934c1682f77d/ring-jetty-adapter/src/ring/adapter/jetty.clj
Signals a request is fully processed and response fully sent.
Signals a request is fully processed and response fully sent. In a perfect world this would be returned only by server adapters when they're done sending the response. But it's useful any time you want to see the result of a handler executing (e.g. in tests).
Functionaliy for translating between Servlet world and Circlet world.
Grab-bag of functions used in multiple places.