Allow streamed client side navigation to be compressed (`gzip`/`brotli`) by proxies
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 20.8k
- Forks
- 2.3k
- Avg merge
- 1d 16h
- Merged PRs (30d)
- 156
Description
Describe the problem
Streamed (defered) client side navigation cannot be compressed by proxies because of the proprietary MIME introduced in https://github.com/sveltejs/kit/pull/9142.
Describe the proposed solution
Next seems to be going for text/x-component for rsc which is a bit strange, and will not resolve the buffering issue tackled by https://github.com/sveltejs/kit/pull/9142.
X-Content-Type-Options=nosniff should prevent browsers from buffering, but the buffering behavior described here will be extended to client side navigation (though it will make it consistent between client side navigation and full page load 🥲).
Alternatives considered
No response
Importance
would make my life easier
Additional Information
Not sure if it should be a bug report.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading pull request #9142 and issue #9154 to understand the streamed navigation response and the buffering behavior involved. Compare the current client-side navigation response with proxy compression requirements, and consider the proposed MIME and nosniff tradeoffs; done means streamed navigation can be compressed by gzip or brotli proxies without reintroducing the buffering problem.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 30/100