-
Notifications
You must be signed in to change notification settings - Fork 3
fix: improve upload server error handling and memory efficiency #419
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
dcalhoun
merged 13 commits into
feat/leverage-host-media-processing
from
feat/improve-media-uploads-and-errors
Apr 9, 2026
Merged
Changes from all commits
Commits
Show all changes
13 commits
Select commit
Hold shift + click to select a range
e9193d6
fix: Avoid "native" term in user-facing errors messages
dcalhoun 32aa39a
fix: drain oversized request body before sending 413 response
dcalhoun 0b6c67b
fix: include CORS headers on server-generated error responses
dcalhoun 0563a94
Revert "fix: include CORS headers on server-generated error responses"
dcalhoun 62d9aee
fix: route 413 response through handler for CORS headers
dcalhoun 0a4cbac
perf(ios): stream multipart upload body from disk instead of memory
dcalhoun 692a891
perf: passthrough upload when delegate does not modify the file
dcalhoun e3d2efe
refactor(android): fix Detekt lint violations
dcalhoun 5e9562d
fix(ios): prevent integer overflow in drain mode byte tracking
dcalhoun f3a08d1
refactor(ios): replace deprecated URL.path with path(percentEncoded:)
dcalhoun 71440d9
refactor(ios): localize "file too large" error via EditorLocalization
dcalhoun 8015719
Revert "refactor(ios): localize "file too large" error via EditorLoca…
dcalhoun 691bb27
fix(ios): review adjustments for #419 (#441)
jkmassel File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The approach of passing server errors to the handler was taken rather than the adding a new
errorResponseHeadersconfiguration (added in 0b6c67b, reverted in 0563a94). The configuration approach leaks host/caller concerns into the library. A similar consideration occurred when implementing authentication bypass for preflightOPTIONSrequests.Ultimately, the 413 responses need to include the correct CORS headers, otherwise the error code and message do not arrive to the client. It instead receives a CORS error.
@jkmassel what do you think of this approach?