With HTTP/2 in every browser, load balancing with automatic failover, IPv6, a sorry page, separate blog server, HTML5 SSE and A+ HTTPS.
Requirements for HTTPS for Local Domains
When connecting to servers on their local network, users are surprised to encounter user interfaces that display errors, show insecure connections, and block some HTTP features when missing a secure context. However, obtaining PKIX certificates for those servers is difficult for a variety of reasons. This document explores requirements for authenticating local servers.
Caddy - The Ultimate Server with Automatic HTTPS
Caddy is a powerful, enterprise-ready, open source web server with automatic HTTPS written in Go
HOW TO: Self-hosting and securing web services out of your home with Argo Tunnel, nginx reverse proxy, Let's Encrypt, Fail2ban (H/T Linuxserver SWAG)
215 votes, 102 comments. Changelog V1.3a - 1 July 2023 DEPRECATED - Legacy tunnels as detailed in this how-to are technically no longer supported…
zeroserve: a zero-config web server you can script with eBPF
zeroserve is a small, fast, zero-config HTTPS server. You hand it a tarball of a website and it serves it - over HTTP/2 and TLS 1.3, with hot reload and a tiny resident footprint. The twist is that you can drop eBPF programs into the tarball and they run on every request, in userspace, as sandboxed middleware - rewriting, authenticating, and rate-limiting requests, or reverse-proxying them to a backend when you want it to act as a gateway in front of your app.
mitmproxy - an interactive HTTPS proxy
mitmproxy is your swiss-army knife for debugging, testing, privacy measurements, and penetration testing. It can be used to intercept, inspect, modify and replay web traffic such as HTTP/1, HTTP/2, HTTP/3, WebSockets, or any other SSL/TLS-protected protocols. You can prettify and decode a variety of message types ranging from HTML to Protobuf, intercept specific messages on-the-fly, modify them before they reach their destination, and replay them to a client or server later on.
OAuth scopes (#3806) · bluesky-social/atproto@1899b1f
* style: prefix `id` and `uri` with `request` where applicable * Dynamically validate OAuth scopes * Allow configuring trusted OAuth clients * Improve client validation * Rework authorization t...
Rate Limiting with NGINX – NGINX Community Blog
One of the most useful, but often misunderstood and misconfigured, features of NGINX is rate limiting. It allows you to limit the amount of HTTP requests a user can make in a given period of time. A request can be as simple as a GET request for the homepage of a website or a POST request on a log‑in form.
Forget about Nginx, I switched to this reverse proxy and it's even better
Traefik is perfect for containerized home labs.
NextGraph - Decentralized, encrypted and local-first platform and framework, towards the better internet we all deserve!
Features a social network, shared documents, productivity tools, an app store, and more! You can use NextGraph for free : resilient, secure, private and encrypted. You own your data and software! Developers can build new web3.0 local-first apps with our open source framework, based on open standards, with CRDTs, E2EE, Linked Data, JSON, Markdown...
Browsers & Standards Work 2026: Call for Community Input
TL;DR: IPFS is planning the next phase of work to make browsers better for the decentralized web – not just IPFS, but any protocol that needs lightweight crypto, peer-to-peer connections, or native browser integration. We need your input on what features matters most. Background: What We’ve Accomplished Over the past 5 years, sustained collaboration with Igalia has delivered real improvements to all major browsers: Ed25519 in WebCrypto API - Shipped in Chrome 137 (May 2025), now available in...
Some notes about HTTP/3
HTTP/3 is going to be standardized. As an old protocol guy, I thought I'd write up some comments. Google (pbuh) has both the most popular ...
Filling the remaining gap between WebSocket, WebRTC and WebTranspor
Existing web platform facilities for network communication include WebSocket and WebRTC. Each mandates a specific protocol, ensures TLS, and respects the Same Origin Policy. The proposed WebTransport is similar in these respects.
Reorganizing Website Architecture for HTTP/2 and Beyond
This document discusses reorganizing website architecture for HTTP/2 and beyond. It summarizes some issues with HTTP/2 including errors in prioritization where some browsers fail to specify resource priority properly. It also discusses the problem of TCP head-of-line blocking where pending data in TCP buffers can delay higher priority resources. The document proposes solutions to these issues such as prioritizing resources on the server-side and writing only what can be sent immediately to avoid buffer blocking. It also examines the mixed success of HTTP/2 push and argues the server should not push already cached resources. - Download as a PDF or view online for free
Important piece of multi-protocol support in browsers! Thanks to much work from Javi, and funding from @ipfs.tech. HEY NOW, settle down - a ways to go: - can only redirect to URLs/paths - no Safari - off by default in Chrome (for now) - only allow-listed schemes unprefixed Step by step...
Javier Fernandez
Blog post about a new Chromium feature I've been working on to allow Web Extensions register protocol handlers just declaring them in the Manifest. blogs.igalia.com/jfernandez/2026/03/24/protoco…
