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
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
CometD 3: RPC, PubSub, Peer-to-Peer Web Messaging
A couple of months ago the CometD Project released its third major version, CometD 3.0.0 (announcement). Since then I wanted to write a blog about this major release, but work on HTTP 2 kept me busy. Today CometD 3.0.1 was