Fix content language initialization and update to use headers backing field #4168
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.
no dev config since its already in #4074
Description
update the backing field for content language to be in the headers instead so that for TransferUtilityDownloadResponse we can easily just copy the headers only instead of the response.ContentLanguage field.
Also was a bug in #4074 where it was always setting the content language in one case because the
ifstatement didnt have brackets. So this fixes that bug and also makes it so the headers is the backing fieldMotivation and Context
Testing
Types of changes
Checklist
License