Don't force default content-type if no content #450
Merged
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
twsouthwick
reviewed
Nov 27, 2023
src/Microsoft.AspNetCore.SystemWebAdapters.CoreServices/SetDefaultResponseHeadersMiddleware.cs
Outdated
Show resolved
Hide resolved
jherven
force-pushed
the
no-default-content-type-for-no-content
branch
from
672cb95 to
27be096
Compare
|
@dotnet-policy-service agree |
…aultResponseHeadersMiddleware.cs Co-authored-by: Taylor Southwick <[email protected]>
How could I miss those. Updated |
twsouthwick
approved these changes
Nov 28, 2023
|
Thanks @jherven for the fix! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Don't force default content-type if no content
If response has no content, don't automatically add content-type header
PR Description
Addresses #449