Fix bug handling HttpResponseMessage that has no content #210
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.
Fixes bug where an error is thrown when the server tries to handle a HttpResponseMessage that does not contain any message content, as is the case when using BaseHttpController helper functions.
Description
Moved code handling content headers inside undefined conditional check.
Related Issue
inversify/InversifyJS#912
Motivation and Context
Fixes bug where server would throw an error with a response that has no content.
How Has This Been Tested?
Tested InversifyExpressServer#handleHttpResponseMessage to ensure the express.Response#sendStatus would be called with a HttpResponseMessage that has no content.
Types of changes
Checklist: