GeezerVison is showing github.com — Set Content-Type explicitly in LargeFileUploadTask. by buptliuhs · Pull Request #502 · microsoftgraph/msgraph-sdk-javascript
Conversation
Summary
In LargefileUploadTask, set Content-Type to application/octet-stream explicitly, otherwise application/json will be used by default, which is not correct.
Motivation
Although using the default application/json does not impact the functionality, if a client using the SDK has something like http-interceptor to examine the request payload, incorrect Content-Type can be misleading, for example, application/json suggests plain/text in json format.
Test plan
N/A
Types of changes
- Bug fix (non-breaking change which fixes an issue)
- New feature (non-breaking change which adds functionality)
- Breaking change (fix or feature that would cause existing functionality to change)
Checklist
- I have read the CONTRIBUTING document.
- My code follows the code style of this project.
- My change requires a change to the documentation.
- I have updated the documentation accordingly.
- I have added tests to cover my changes.
- All new and existing tests passed.
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Tony Liu (@buptliuhs) Thanks again for your contribution!!
I will review this next week.
Question for you, are you facing an error with the current code that is setting the default header to application/json ?
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
|
Nikitha Chettiar (@nikithauc) , No, files can be successfully uploaded even the header is set to application/json by default, so I guess the API server just doesn't check it. This is NOT actually impacting the file upload functionality.
However, as I mentioned, it is not uncommon, on the client-side, there is logic like http-interception doing things logs, audits, and etc. Having application/json in the header is misleading and can cause unexpected behaviours.
No unit test updated for now since the existing part of the code is not covered in any test cases. I can add some (of course need to do some refactoring to make it testable) if it is needed.
Thanks!
|
Sorry, something went wrong.
Uh oh!
There was an error while loading. Please reload this page.
Reviewers
1 more reviewer
Reviewers whose approvals may not affect merge requirements
Uh oh!
There was an error while loading. Please reload this page.
Milestone
No milestone
Development
Successfully merging this pull request may close these issues.
Uh oh!
There was an error while loading. Please reload this page.
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.
|