What changed for people who run xenia, newest first. Each release’s notes, with the details, are its tag message and its page on the releases repo.
Trust, packages for Debian, FreeBSD and Homebrew, and the gaps users hit first: what 0.15.1 got wrong in the open, conformance, single-file routes, limits on connections and requests in flight, and docs to start from.
-----BEGIN PRIVATE KEY-----, what openssl req -newkey rsa:2048 writes) now load, in tls.certificates and as an upstream’s tls.key. Every release with TLS refused them as “the key does not match the certificate”, because Mbed TLS cannot compare such a key with its certificate; xenia now compares the two public keys itself, and still refuses a key that is not the certificate’s. The same key in PKCS#1 form (BEGIN RSA PRIVATE KEY) and EC keys always worked.{ path: '/robots.txt', file: 'public/robots.txt' } serves one file, with everything a file route does: validators, ranges, precompressed copies, gzip and the small-file cache. With a prefix, it serves the file for every path under it, the fallback a single-page app needs: { prefix: '/', file: 'dist/index.html' }, while longer prefixes keep their own routes. See Single files.inFlight, with or without a rate; one more gets 429. Behind trustedProxies the client is the one X-Forwarded-For names; a WebSocket counts until it closes. “Rate limits” in the docs is now Limits.aborted. Before, a client that closed only its side still got the response; it still does once the response has begun.server.maxConnectionsPerClient closes a client’s connections past that many as soon as they are accepted. It counts the connection’s own address, and leaves trusted proxies out. Off unless set.xenia-server-VERSION-freebsd-amd64.pkg, in each release, covered by SHA256SUMS. The package installs an rc.d script (sysrc xenia_enable=YES, service xenia start) that runs xenia on port 80 under daemon(8), serving as the user xenia, and the example project in /usr/local/etc/xenia. --user sets no new privileges there too, as on Linux. See Deployment.xenia-server_VERSION_amd64.deb and _arm64.deb, covered by the signed SHA256SUMS. A package installs the static binary as /usr/bin/xenia, the systemd unit, the example project in /etc/xenia (conffiles, root:xenia), the user xenia and a logrotate entry, and enables and starts the service. apt purge removes the config and logs, and keeps the user. See Deployment.brew install xenia-platform/tap/xenia-server, then brew services start xenia-server to run it on 127.0.0.1:8080.Content-Length, even with the same value, is 400;Transfer-Encoding with empty list elements (, chunked) is 501: only a lone chunked is chunked;Transfer-Encoding (chunked\t) is 400: whitespace to xenia, another coding to some;;name, ;name=token or ;name="quoted");name: value, and never Content-Length, Transfer-Encoding or Connection;http://user@host/) is 400.The chunked rules hold for upstream responses too.
xenia_cache_fills_continued_total. /snapshot also counts the requests that waited for another’s fill (waited).tls.redirectPort: the port HTTPS redirects send clients to, when it isn’t the one xenia listens on: behind -p 443:8443, redirectPort: 443. Without it, as before, the first --listen-tls port. It changes with a reload; xenia check and GET /snapshot show it.THIRD_PARTY_LICENSES, which its README and security policy point to.defineConfig, so editors check it as it is copied; a bare export default { … } still works.Content-Length, even with the same value (400); Transfer-Encoding with empty list elements (501) or a tab (400); whitespace after a chunk size, and chunk extensions outside their grammar; trailers that are not name: value, or that name Content-Length, Transfer-Encoding or Connection; and absolute-form targets with userinfo (400). Clients that follow the standard send none of these: if one of yours starts getting 400 or 501, its framing is why. The chunked rules hold for upstream responses too."status": null and "aborted": true. A client that half-closes on purpose after sending its request no longer gets an answer; once the answer has begun, it still does.tls.redirect, redirects name the port of the first --listen-tls, as before. Behind a mapping such as -p 443:8443, set the new tls.redirectPort: 443 so they name the port clients reach.GET /snapshot. A limit’s rate is null when it has only inFlight, and the JSON has new keys: file on file routes, inFlight and its counts on limits, maxConnectionsPerClient in the server settings. A script that reads it should expect them.#rate-limits still land there./usr/bin/xenia and its unit in /usr/lib/systemd/system. The archive’s install steps put them in /usr/local/bin/xenia and /etc/systemd/system/xenia.service, and a unit there wins over the package’s, so it would keep starting the old binary. Before installing the package, stop the service and remove both, keeping any listener changes as a systemctl edit xenia override. /etc/xenia stays as it is: dpkg asks before it replaces a config file you already have, and keeps yours unless told otherwise.The first public release; 0.15.0 was not published.
Distribution: a Docker image, signed releases, and a license for the binaries.
ofkindness/xenia for amd64 and arm64, from the same static binary as the archives: no shell, runs as uid 65532 on 8080/8443, config in /etc/xenia, a healthcheck through the admin socket, the access log on stdout. See docs/docker.md.--access-log - writes the access log to standard output.SHA256SUMS are signed with Sigstore (cosign, keyless), and each release has an SPDX SBOM of xenia and every library in it.Operability: running as a service.
--user USER[:GROUP]: started as root, xenia binds its ports, then becomes that user for good, before anything else runs.NOTIFY_SOCKET (Type=notify-reload), and contrib/systemd/xenia.service is a unit to start from.server.trustedProxies name is the X-Forwarded-For sent upstream and the access log’s client, with the proxy in peer.x-content-type-options: nosniff on everything xenia makes itself; file ETags include the inode.Hardening: every high and medium finding of a full review.
X-Forwarded-*, Forwarded and X-Real-IP never go upstream; cache keys include the scheme; verified client certificates bypass the cache; strict chunk sizes.Project configs.
xenia.conf.js, found where xenia starts, and imports the project’s own ./ and ../ modules.xenia types writes xenia.d.ts for editors to check configs with; xenia check validates one.Serving stale (RFC 5861).
stale-while-revalidate: stale entries are served at once while one background refresh renews them.stale-if-error: a kept entry answers when the upstream fails.staleWhileRevalidate and staleIfError where responses say nothing.Upstream hostnames.
host:port; every address a name resolves to is a server of its own, refreshed every resolveInterval.xenia ctl resolve and drains by name.Response caching for proxy routes.
Vary, revalidation, request coalescing across workers, gzip copies and purging (xenia ctl cache purge).Rate limits.
rate, burst) per client, shared by routes that name them, exact across workers; 429 with retry-after; clients behind server.trustedProxies taken from X-Forwarded-For.Compression.
vary: accept-encoding.HTTP/2 for clients.
Observability.
--metrics), request IDs (x-request-id), and the admin interface over TCP with a token.HTTP caching for files.
Last-Modified, conditional requests (304, 412) and single ranges (206, 416).Static files.
root, index, listing, precompressed, followSymlinks, contentTypes, with safe paths and a small-file cache.The first release.
SIGHUP.