fix(supabase): disable Kong response buffering for storage to support large file downloads #7864
Conversation
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
1 participant
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.
Changes
When downloading large files (1GB+) from Supabase Storage, Kong buffers the response to a temporary file. This causes
upstream prematurely closed connectionerrors during long-running downloads.Kong logs show:
[warn] an upstream response is buffered to a temporary file /usr/local/kong/proxy_temp/...
[error] upstream prematurely closed connection while reading upstream
Solution
Disable request/response buffering and increase timeouts for the storage-v1 service:
response_buffering: false- stream directly to client without bufferingrequest_buffering: false- stream uploads without bufferingread_timeout: 3600- 1 hour for large downloadswrite_timeout: 3600- 1 hour for large uploadsSettings are configurable via environment variables with sensible defaults.