Changelog

We recently talked with Daniel Stenberg about HTTP/2 and QUIC, so this news comes with little surprise looking back on that conversation with hindsight. The protocol that’s been called HTTP-over-QUIC for quite some time has now changed name and will officially become HTTP/3. This was triggered by this original suggestion by Mark Nottingham. On November 7, 2018 Dmitri of Litespeed announced that they and Facebook had successfully done the first interop ever between two HTTP/3 implementations. Mike Bihop’s follow-up presentation in the HTTPbis session on the topic can be seen here. The consensus in the end of that meeting said the new name is HTTP/3!

Handling dynamic virtual hosts, load balancing, proxying web sockets and SSL encryption should be easy and robust. I agree! With built-in support for clustering, HTTP/2, LetsEncrypt, and Docker, this is worth a look. 👀

This was announced in late March, but I missed it back then so maybe you did too. Our goal was to more easily enable anyone to explore the health of the web as a whole. Not just data-mining SQL gurus or statisticians, but everyone with a vested interest in the state of the web. An excellent goal, indeed. How did they do? Well, they added a bunch of awesome reports and consolidated traffic data between mobile and desktop devices. If you hadn’t bookmarked this site previously, now is the time.

NuSTER can be used as a RESTful NoSQL cache server, using HTTP POST/GET/DELETE to set/get/delete Key/Value object. It can be used as an internal NoSQL cache sits between your application and database like Memcached or Redis as well as a user facing NoSQL cache that sits between end user and your application. It supports headers, cookies, so you can store per-user data to same endpoint.

A common discrepancy between our dev and prod environments is that prod uses HTTPS while dev is stuck on HTTP because reasons: Using certificates from real CAs for development can be dangerous or impossible (for hosts like localhost or 127.0.0.1), but self-signed certificates cause trust errors. Managing your own CA is the best solution, but usually involves arcane commands, specialized knowledge and manual steps. I’ve considered getting my dev environment on HTTPS but have always stopped at “Managing your own CA”. 🙅‍♂️ Not gonna do it. But! mkcert automatically creates and installs a local CA in the system root store, and generates locally-trusted certificates. mkcert currently supports macOS and Linux. Windows support coming next.

A new minimal, extensible, fast and productive framework for building HTTP APIs with Python. Featuring request validation, dependency injection, functional middleware, and more.

Upload a file using curl: curl --upload-file ./hello.txt https://transfer.sh/hello.txt And the response will be a shareable URL, e.g. https://transfer.sh/eibhM/hello.txt Works with files up to 10GB, deletes them after 14 days, costs nothing, and encrypts everything. Super cool! 😎

Chris James: Write a simple web server in Go with test driven development. Learn how to use mocking to let you break the problem down into small iterative chunks. All using standard library, source code is available to read. The linked page is a sub-section of the Learn Go with tests GitBook. Do you enjoy TDD and want to learn Go? Or do you enjoy Go and want to learn TDD? Either way, this looks like a great (WIP) resource.

Lin Clark strikes again with her ridiculously well done code cartoons. This time, she’s taking on the task of explaining why Mozilla is championing DNS over HTTPS. (Curious about Lin, her teaching efforts, and her work at Mozilla? GOTO 294.)

Daniel Stenberg joined the show to talk about 20 years of curl, what’s new with http2, and the backstory of QUIC - a new transport designed by Jim Roskind at Google which offers reduced latency compared to that of TCP+TLS+HTTP/2.

Flare listens to changes on HTTP endpoints and notify subscripted clients about the changes. It help reduce the pressure on APIs by avoiding the clients to do pooling requests to search for new/changed content and the need of the APIs to develop workers to notify the clients about the. Pitched as useful for microservice architectures, but could find lots of uses outside of that context too.

At this time in 1998 Titanic was winning 11 Oscars, My Heart Will Go On was topping the music charts, and Daniel Stenberg was uploading the first public release of one of the most useful tools in Internet history. In this birthday post, Daniel walks down memory lane and says what those first few years were like: It was far from an immediate success. An old note mentions how curl 4.8 (released the summer of 1998) was downloaded more than 300 times from the site. We talked about curl on The Changelog when it was 17 years old. I think It’s time to bring Daniel back on to celebrate the big Two Oh. 🎊

Jordan shared this super fun project in our Slack and hilarity ensued. 10/10 would meme again 🎖