87c24e7258
* Fixes #8405 - onAllDataRead() is called twice under h2 if the stream times out Per Servlet semantic, HTTP/2 stream timeout should be ignored. The code was trying to fail the read via `_contentDemander.onTimeout()`, but then it was still calling `onContentProducible()`, which was returning `true` because the state of the read was IDLE (all the request content was read) and the request was suspended. Now the code checks if the read was really failed; if it is not, then `onContentProducible()` is not called and so the idle timeout is ignored. Signed-off-by: Simone Bordet <simone.bordet@gmail.com> |
||
|---|---|---|
| .github | ||
| .mvn | ||
| apache-jsp | ||
| apache-jstl | ||
| build-resources | ||
| demos | ||
| documentation | ||
| javadoc | ||
| jetty-alpn | ||
| jetty-annotations | ||
| jetty-ant | ||
| jetty-bom | ||
| jetty-cdi | ||
| jetty-client | ||
| jetty-deploy | ||
| jetty-fcgi | ||
| jetty-gcloud | ||
| jetty-hazelcast | ||
| jetty-home | ||
| jetty-http | ||
| jetty-http-spi | ||
| jetty-http2 | ||
| jetty-http3 | ||
| jetty-infinispan | ||
| jetty-io | ||
| jetty-jaas | ||
| jetty-jaspi | ||
| jetty-jmx | ||
| jetty-jndi | ||
| jetty-jspc-maven-plugin | ||
| jetty-keystore | ||
| jetty-maven-plugin | ||
| jetty-memcached | ||
| jetty-nosql | ||
| jetty-openid | ||
| jetty-osgi | ||
| jetty-p2 | ||
| jetty-plus | ||
| jetty-proxy | ||
| jetty-quic | ||
| jetty-quickstart | ||
| jetty-rewrite | ||
| jetty-runner | ||
| jetty-security | ||
| jetty-server | ||
| jetty-servlet | ||
| jetty-servlets | ||
| jetty-slf4j-impl | ||
| jetty-start | ||
| jetty-unixdomain-server | ||
| jetty-unixsocket | ||
| jetty-util | ||
| jetty-util-ajax | ||
| jetty-webapp | ||
| jetty-websocket | ||
| jetty-xml | ||
| logos | ||
| scripts | ||
| tests | ||
| .gitattributes | ||
| .gitignore | ||
| .lgtm.yml | ||
| CODE_COVERAGE.md | ||
| CODE_OF_CONDUCT.md | ||
| CONTRIBUTING.md | ||
| Jenkinsfile | ||
| Jenkinsfile-autobahn | ||
| Jmh_Jenkinsfile | ||
| KEYS.txt | ||
| LICENSE | ||
| NOTICE.txt | ||
| README.md | ||
| SECURITY.md | ||
| VERSION.txt | ||
| header-template.txt | ||
| pom.xml | ||
README.md
Eclipse Jetty Canonical Repository
This is the canonical repository for the Jetty project, feel free to fork and contribute now!
Submitting a patch or pull request?
Make sure you have an Eclipse Contributor Agreement (ECA) on file.
Project description
Jetty is a lightweight highly scalable java based web server and servlet engine. Our goal is to support web protocols like HTTP, HTTP/2 and WebSocket in a high volume low latency way that provides maximum performance while retaining the ease of use and compatibility with years of servlet development. Jetty is a modern fully async web server that has a long history as a component oriented technology easily embedded into applications while still offering a solid traditional distribution for webapp deployment.
Webapp Example
$ mkdir base && cd base
$ java -jar $JETTY_HOME/start.jar --add-modules=http,deploy
$ cp ~/src/myproj/target/mywebapp.war webapps
$ java -jar $JETTY_HOME/start.jar
Embedded Example
Server server = new Server(port);
ServletContextHandler context = new ServletContextHandler(server, "/");
context.addServlet(MyServlet.class, "/*");
server.start();
Documentation
Project documentation is available on the Jetty Eclipse website.
Building
Apache Maven 3.8.0 and OpenJDK requirements:
| Branch | Maven Version | Minimum JDK | Recommended JDK |
|---|---|---|---|
jetty-10.0.x |
Maven 3.8.6+ | OpenJDK 11 | OpenJDK 17 (for optional loom and http/3 support) |
jetty-11.0.x |
Maven 3.8.6+ | OpenJDK 11 | OpenJDK 17 (for optional loom and http/3 support) |
jetty-12.0.x |
Maven 3.8.6+ | OpenJDK 17 | OpenJDK 17 |
Full Build with All Tests:
mvn clean install
Fast Build if you need jars and distribution (not running tests, checkstyle, enforcer, license check):
mvn -Pfast clean install
Optional build tools:
graphviz- used by asciidoctor in the jetty-documentation build to produce various graphsDocker- used to run some integration tests for testing third party integrations
Once the build is complete, you can find the built Jetty Maven artifacts in your Maven local repository. Along with the following locations of note:
| Branches | Location | Description |
|---|---|---|
| all | jetty-home/target/jetty-home-<ver>.tar.gz |
The Jetty Home standalone tarball |
jetty-10.0.x |
jetty-runner/target/jetty-runner-<ver>.jar |
The Jetty Runner uber jar |
jetty-11.0.x |
jetty-runner/target/jetty-runner-<ver>.jar |
The Jetty Runner uber jar |
jetty-12.0.x |
jetty-ee10/jetty-ee10-runner/target/jetty-ee10-runner-<ver>.jar |
The Jetty Runner uber jar for ee10/Servlet 6 (jakarta.servlet) webapps |
jetty-12.0.x |
jetty-ee9/jetty-ee9-runner/target/jetty-ee9-runner-<ver>.jar |
The Jetty Runner uber jar for ee9/Servlet 5 (jakarta.servlet) webapps |
jetty-12.0.x |
jetty-ee8/jetty-ee8-runner/target/jetty-ee8-runner-<ver>.jar |
The Jetty Runner uber jar for ee8/Servlet 4 (javax.servlet) webapps |
Note: The build 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 (check your ulimit -n value).
Professional Services
Expert advice and production support are available through Webtide.com.