eclipseembeddedfcgihttphttp-clienthttp-serverhttp2http2-pushhttp3httpsjakartaeejavajettyjsposgiservletssltlsunix-socketwebsockets
e94ff7db9c
before the connect timeout. The changes to fix this issue uncovered problems in the HttpSender state machine. In particular, the SenderState is now defining more states that depend on deferred content, and on handling of 100 Continue responses. The refactoring also highlighted the fact that there was no need to keep HttpConversation objects in a Map in HttpClient: they are now only referenced by the HttpRequest. With this change, Request.getConversationID() has been deprecated. Also fixed a number of tests to make them more reliable. |
||
---|---|---|
LICENSE-CONTRIBUTOR | ||
aggregates | ||
dists | ||
examples | ||
jetty-annotations | ||
jetty-ant | ||
jetty-client | ||
jetty-continuation | ||
jetty-deploy | ||
jetty-distribution | ||
jetty-http | ||
jetty-http-spi | ||
jetty-io | ||
jetty-jaas | ||
jetty-jaspi | ||
jetty-jmx | ||
jetty-jndi | ||
jetty-jsp | ||
jetty-jspc-maven-plugin | ||
jetty-maven-plugin | ||
jetty-monitor | ||
jetty-nosql | ||
jetty-osgi | ||
jetty-overlay-deployer | ||
jetty-plus | ||
jetty-proxy | ||
jetty-rewrite | ||
jetty-rhttp | ||
jetty-runner | ||
jetty-security | ||
jetty-server | ||
jetty-servlet | ||
jetty-servlets | ||
jetty-spdy | ||
jetty-spring | ||
jetty-start | ||
jetty-util | ||
jetty-util-ajax | ||
jetty-webapp | ||
jetty-websocket | ||
jetty-xml | ||
tests | ||
.gitattributes | ||
.gitignore | ||
LICENSE-eplv10-aslv20.html | ||
NOTICE.txt | ||
README.TXT | ||
VERSION.txt | ||
header-template.txt | ||
icon.jpg | ||
pom.xml | ||
settings.xml |
README.TXT
This is a source checkout of the Jetty webserver. To build, use: mvn clean install The jetty distribution will be built in jetty-distribution/target/distribution The first build may take a long time as Maven downloads all the dependencies. The tests do a lot of stress testing, and on some machines it is necessary to set the file descriptor limit to greater than 2048 for the tests to all pass successfully. Bypass tests by building with -Dmaven.test.skip=true but note that this will not produce some test jars that are leveraged in other places in the build.