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 growth that was not anticipated in the late ’90s. With Read more…
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 sockets based on JEP 380, which shipped with Java 16. Read more…
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 to a Servlet Container such as Jetty or Tomcat. This Read more…
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 cleartext HTTP/1.1 and cleartext HTTP/2 on the same server port. Read more…
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 released, so it’s time for a new CometD blog entry. Read more…
Introduction One of the big refactorings in Jetty 9 is the complete rewrite of the HTTP client. The reasons behind the rewrite are many: We wrote the codebase several years ago; while we have actively maintained, it was starting to show its age. The HTTP client guarded internal data structures from Read more…