WW-5602 Fix StreamResult contentCharSet handling and refactor for extensibility #1510
+360
−80
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
contentCharSetis an expression that evaluates to null, the content-type header was incorrectly appending;charset=with no valueStreamResultto improve extensibility and code qualityChanges
Bug Fix (WW-5602)
contentCharSetexpression before checking for emptinesssetCharacterEncoding(null)to clear Dispatcher's default UTF-8 encoding when no charset is specifiedRefactoring
DEFAULT_BUFFER_SIZE,DEFAULT_CONTENT_TYPE,DEFAULT_CONTENT_DISPOSITION,DEFAULT_INPUT_NAMEprotectedmethods for easy extension:resolveInputStream()- custom stream sources (database, cloud, generated)applyResponseHeaders()- custom headers (ETag, X-Custom)applyContentLength()- custom length calculationstreamContent()- custom buffering, compression, encryptionTest plan
StreamResultTesttests passtestStreamResultWithNullCharSetExpressionverifies the bug fixCloses WW-5602
🤖 Generated with Claude Code