stackchain/stackchain-dashboard
1
0
Fork 0
Code Issues 9 Pull Requests 1 Actions Packages Projects Releases 713 Wiki Activity

Compress the mobile dashboard shell over HTTP #417

New Issue
Closed
opened 2026-08-09 18:29:50 +00:00 by rockachopa · 0 comments
rockachopa commented 2026-08-09 18:29:50 +00:00
Member
Copy Link

Problem

The fingerprinted mobile runtime is about 425 KB and the dashboard shell is about 498 KB before icons, but the FastAPI application does not negotiate HTTP compression. The existing bundle test only proves a hypothetical gzip size (about 98 KB for the shell); production still transfers raw bytes. This slows cold launch, service-worker installation, and runtime updates on constrained mobile networks.

Scope

  • Negotiate gzip for substantial dashboard shell responses and JSON payloads.
  • Preserve immutable/no-cache and security headers.
  • Keep identity responses byte-identical and avoid compressing small responses.
  • Verify behavior at the ASGI request boundary rather than only computing build-time gzip size.

Acceptance tests

  • A runtime request with Accept-Encoding: gzip returns Content-Encoding: gzip, Vary: Accept-Encoding, a compressed content length at most 100 KiB, and decompresses exactly to the built runtime.
  • The same runtime with Accept-Encoding: identity is unencoded and byte-identical.
  • Dashboard HTML and CSS are compressed when accepted while retaining their cache and security headers.
  • Small responses are not compressed.
  • The full test suite passes.

No historical issue or recent commit implements wire-level HTTP compression. Issue #379 bundled and fingerprinted the runtime but only added a computed gzip budget; this issue realizes that transfer reduction.

## Problem The fingerprinted mobile runtime is about 425 KB and the dashboard shell is about 498 KB before icons, but the FastAPI application does not negotiate HTTP compression. The existing bundle test only proves a hypothetical gzip size (about 98 KB for the shell); production still transfers raw bytes. This slows cold launch, service-worker installation, and runtime updates on constrained mobile networks. ## Scope - Negotiate gzip for substantial dashboard shell responses and JSON payloads. - Preserve immutable/no-cache and security headers. - Keep identity responses byte-identical and avoid compressing small responses. - Verify behavior at the ASGI request boundary rather than only computing build-time gzip size. ## Acceptance tests - A runtime request with `Accept-Encoding: gzip` returns `Content-Encoding: gzip`, `Vary: Accept-Encoding`, a compressed content length at most 100 KiB, and decompresses exactly to the built runtime. - The same runtime with `Accept-Encoding: identity` is unencoded and byte-identical. - Dashboard HTML and CSS are compressed when accepted while retaining their cache and security headers. - Small responses are not compressed. - The full test suite passes. No historical issue or recent commit implements wire-level HTTP compression. Issue #379 bundled and fingerprinted the runtime but only added a computed gzip budget; this issue realizes that transfer reduction.
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels   
P0

Drop everything

  
P1

High priority

  
P2

Medium priority

  
agent:nightprowl

Assignments routed to the LongCat NightProwl evaluation worker

  
backend

Backend service

  
ci

Continuous integration / actions

  
frontend

Frontend / UI

  
meta

Meta / planning

  
pages

Gitea Pages

  
template

Repo template / standards

No Label
P0
P1
P2
agent:nightprowl
backend
ci
frontend
meta
pages
template
Milestone
Clear milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
No Assignees
1 Participants
Notifications
Due Date
The due date is invalid or out of range. Please use the format 'yyyy-mm-dd'.

No due date set.

Dependencies

No dependencies set.

Reference: stackchain/stackchain-dashboard#417
No description provided.
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?