jetty.project
jetty.project copied to clipboard
jetty
Eclipse Jetty® - Web Container & Clients - supports HTTP/2, HTTP/1.1, HTTP/1.0, websocket, servlets, and more
**Jetty version(s)** https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-p2/10.0.10/ **Description** I have downloaded the zip but if I look at the artifacts.xml is empty: ``` ``` **How should it looks like** If I look at https://repo1.maven.org/maven2/org/eclipse/jetty/jetty-p2/10.0.9/...
**Jetty version(s)** 12.0.x **Description** Fails with `org.eclipse.jetty.client.HttpClientTLSTest expected an empty collection but within 5 seconds.` See: https://jenkins.webtide.net/job/jetty.project/job/jetty-12.0.x/396/testReport/junit/org.eclipse.jetty.client/HttpClientTLSTest/testEncryptedOutputBufferRepoolingAfterNetworkFlushThrows_boolean__2_/
Alternative implementation of support for virtual threads for HTTP/1.1, HTTP/2 and HTTP/3. The virtual thread support is in AdaptiveExecutionStrategy. When virtual threads are supported and enabled, reserved threads are disabled...
Make ee10 `DefaultServlet` able to serve jetty-dir.css
- ee8 demos to use ee9 demos resources - add jetty-ee8-demo-jaas-webapp - add jetty-ee8-demo-jndi-webapp jetty-ee8-demo-mock-resources - uhm jetty-ee8-demo-jetty-webapp have some issues - uhm jetty-ee8-demo-jetty-webapp have some issues - fix jetty-ee8-demo-jetty-webapp...
This fixes a few things with the URI matching done in `MetaInfConfiguration` against the regex from `CONTAINER_JAR_PATTERN` and `WEBINF_JAR_PATTERN`. 1. The old `PatternMatcher` usage introduced an extra unnecessary `newResource()` call...
Reworked the `PathResource.checkAliasPath` ... If the URI is a `jar:file:` based, the URI only check is skipped and the path segment checks still apply. Also, the symlink check is skipped...
Jetty 12 alias checking needs to be reviewed and fixed. AliasCheck is an interface defined in jetty-core but is only used in the ee10 servlet ContextHandler and is not used...
- Strengthen contract of WebSocket upgrade methods by defining in javadoc that an error response needs to be generated by them if they are not returning a WebSocket Object. -...