Release 1.71.3

Release date: August 16, 2026

Release Notes - Seatmap Platform

Version 1.71.3 - 2026-08-16

Release Focus: A smaller renderer download where your proxy supports brotli. The booking-client container can now delegate response compression to the ingress in front of it. Delivered as a patch on top of the 1.71 line.

MetaTitle: Release 1.71.3: Smaller Renderer Download - Seatmap.pro

MetaDescription: Seatmap 1.71.3 lets the booking-client container delegate compression to your proxy, cutting the renderer download where brotli is supported.

What’s Improved

The renderer bundle can be served smaller

The booking-client container compresses its own responses with gzip. Because a response that already carries a content encoding cannot be recompressed, the proxy in front of it can never apply a better algorithm, and every client receives gzip regardless of what it supports.

The container can now be told to serve responses uncompressed and leave compression to the ingress or reverse proxy. Where that proxy supports brotli, browsers receive it instead:

Asset	gzip	brotli	Saved
`seatmap-booking-renderer.js`	289 KB	230 KB	59 KB (20.5%)
`seatmap-admin-renderer.js`	287 KB	229 KB	58 KB (20.3%)

Clients that do not advertise brotli continue to receive gzip from the proxy, so nothing regresses for older integrations.

This is opt-in. The container compresses with gzip unless told otherwise, so deployments that do nothing keep their current behaviour.

Issue: SEAT-1167.

Affected products

booking-client — new DELEGATE_COMPRESSION setting to hand compression to the proxy.

Upgrade

No API, configuration or database changes, and no action is required.

To take up the improvement, confirm that the ingress or reverse proxy in front of the container compresses responses and supports brotli, then set DELEGATE_COMPRESSION=true on the container. With the Helm chart this is the booking.frontend.delegateCompression value:

booking:
  frontend:
    delegateCompression: true

Leave it unset to keep the container compressing with gzip as before. Do not enable it unless the proxy in front of the container compresses, or responses will be served uncompressed.