Fix fallback for unknown Content-Type values (#7034)#7132
Open
raashish1601 wants to merge 1 commit intoexpressjs:masterfrom
Open
Fix fallback for unknown Content-Type values (#7034)#7132raashish1601 wants to merge 1 commit intoexpressjs:masterfrom
raashish1601 wants to merge 1 commit intoexpressjs:masterfrom
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.
This updates the response/content-type fallback path for
#7034and adds coverage in bothres.setand utils tests, plus the runtime/sendand/endchecks that reproduced the issue.Validation:
npx mocha --require test/support/env --reporter spec --check-leaks test/res.set.js test/utils.jsnpx eslint lib/response.js lib/utils.js test/res.set.js test/utils.jsnode+supertestcheck for/sendand/end