Repository navigation
perf(edge): enable gzip compression and configure client request buffer limits - #2
Merged
Merged
Conversation
…er limits - Configured gzip compression (level 5, min_length 256 bytes) across text, JSON, and XML MIME types to reduce edge egress bandwidth and latency. - Set explicit client body (128k) and header buffer (1k default, 4x8k large) thresholds to prevent memory fragmentation and slowloris vector expansion. - Added automated unit test coverage in tests/test_project.py.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary & Motivation
Edge proxies terminating TLS and routing to internal upstream pools must optimize both payload compression and ingress buffer allocation to protect downstream application pods from oversized headers and buffer exhaustion.
Key Changes