mirror of
https://github.com/NginxProxyManager/nginx-proxy-manager.git
synced 2026-04-25 09:25:55 +03:00
[GH-ISSUE #713] Add Brotli Support #602
Labels
No labels
awaiting feedback
bug
cannot reproduce
dns provider request
duplicate
enhancement
enhancement
enhancement
good first issue
help wanted
invalid
need more info
no certbot plugin available
product-support
pull-request
question
stale
troll
upstream issue
v2
v2
v2
v3
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/nginx-proxy-manager-NginxProxyManager#602
Loading…
Add table
Add a link
Reference in a new issue
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?
Originally created by @arlllk on GitHub (Nov 11, 2020).
Original GitHub issue: https://github.com/NginxProxyManager/nginx-proxy-manager/issues/713
Add the capability to use Brotli in the reverse proxy as a compression option. The official nginx module repository is currently active
@hitchhooker commented on GitHub (Aug 12, 2021):
Has anybody come up with a fork or workaround to add brotli?
@jc21 commented on GitHub (Aug 13, 2021):
Notes for anyone considering adding this:
Compressionand then select between gzip and brotli (if I understand this correctly)@xrh0905 commented on GitHub (Jul 31, 2023):
Hi. I'm currently trying to work on it, but I'm new to these.
So,from what I can tell, Brotli support needs to be added upstream, which I opened a PR for that.
However, I'm not good at databases nor at frontend. And I guess it's safe to just leave brotli on as default.
It's should just work if you put
brotli on;in thenginx.conf.Please correct me if I'm wrong.
Sorry for any grammer mistakes or misspelling. My English is poor.
@github-actions[bot] commented on GitHub (Mar 23, 2024):
Issue is now considered stale. If you want to keep it open, please comment 👍
@github-actions[bot] commented on GitHub (May 4, 2025):
Issue was closed due to inactivity.
@PraveenAlexis commented on GitHub (Dec 5, 2025):
any update on this?
@leloyo commented on GitHub (Jan 16, 2026):
Any update on this? Happy to see if someone is willing to take the leap and move forward with the implementation ?