web-server: add compression
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.2k
- Forks
- 232
- Avg merge
- 11h 35m
- Merged PRs (30d)
- 60
Description
In my mind, this could be solved via:
- adding a reverse proxy to the container (NGINX, Caddy) and enabling compression
- adding a compression middleware to axum
I assume axum is fine being exposed to the internet and doesn't need to be behind a reverse proxy (?).
Also in our current NGINX config: IP blocks, while it's unclear if we would handle this in AWS / CloudFront, or if we would have to handle this in our webserver (see https://github.com/rust-lang/simpleinfra/issues/353)
Contributor guide
No contributing guide indexed for this repository
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 locating the docs.rs web-server deployment and current NGINX configuration; the issue does not name specific files or tests. Compare compression in an axum middleware with a reverse-proxy approach, and resolve where IP blocks belong between AWS/CloudFront and the web server. Done means the deployment approach is decided and compression is enabled with its security implications addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, nginx, rust
- Domain
- backend, cloud, infrastructure, networking
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100