Introduction HTTP/3 is the next iteration of the HTTP protocol. HTTP/1.0 was released in 1996 and HTTP/1.1 in 1997; HTTP/1.x is a fairly simple textual protocol based on TCP, possibly wrapped in TLS, that experienced over the years a tremendous
UnixDomain Support in Jetty
UnixDomain sockets support was added in Jetty 9.4.0, back in 2015, based on the JNR UnixSocket library. The support for UnixDomain sockets with JNR was experimental, and has remained so until now. In Jetty 10.0.7/11.0.7 we re-implemented support for UnixDomain
Introducing Jetty Load Generator
The Jetty Project just released the Jetty Load Generator, a Java 11+ library to load-test any HTTP server, that supports both HTTP/1.1 and HTTP/2. The project was born in 2016, with specific requirements. At the time, very few load-test tools
Reactive HttpClient 1.1.5, 2.0.0 and 3.0.0
Following the releases of Eclipse Jetty 10.0.0 and 11.0.0, the Reactive HttpClient project — introduced back in 2017 — has released versions 1.1.5, 2.0.0 and 3.0.0. Reactive HttpClient 1.1.x Series Reactive HttpClient Versions 1.1.x, of which the latest is the
Object Pooling, Benchmarks, and Another Way
Context The Jetty HTTP client internally uses a connection pool to recycle HTTP connections, as they are expensive to create and dispose of. This is a well-known pattern that has proved to work well. While this pattern brings great benefits,
Eat What You Kill without Starvation!
Jetty 9 introduced the Eat-What-You-Kill[1]The EatWhatYouKill strategy is named after a hunting proverb in the sense that one should only kill to eat. The use of this phrase is not an endorsement of hunting nor killing of wildlife for food
Jetty ReactiveStreams HTTP Client
ReactiveStreams has gained a lot of attention recently, especially because of its inclusion in JDK 9 in the Flow class. A number of libraries have been written on top of ReactiveStreams that provide a functional-style API that makes asynchronous processing
Jetty, Cookies and RFC6265 Compliance
Starting with patch 9.4.3, Jetty will be fully compliant with RFC6265, which presents changes to cookies which may have significant impact for some users. Up until now Jetty has supported Version=1 cookies defined in RFC2109 (and continued in RFC2965) which allows for special/reserved
HTTP/2 with HAProxy and Jetty
HTTP/2 is now the official RFC 7540, and it’s about time to deploy your website on HTTP/2, to get the numerous benefits that HTTP/2 brings. A very typical deployment is to have Apache (or Nginx) working as a reverse proxy
Jetty HTTP/2 cleartext upgrade
With the approach of the release candidate for Jetty 9.3.0 in the next days, we have implemented support for HTTP/2 cleartext upgrade mechanism, on server side, resolving issue #465857. This means that you can configure a Jetty server to speak