This repository has been archived by the owner on Jul 10, 2022. It is now read-only.
fix Content-Type to same type as official repository #146
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.
I think the Content-Type should be same as official repository.
https://gist.github.com/mtanda/5d02c0b2b6a8f8abfd2bfe1ec519641d
The motivation to fix Content-Type is, I want to access S3 hosted repository from API Gateway.
https://docs.aws.amazon.com/apigateway/latest/developerguide/integrating-api-with-aws-services-s3.html
I'm not sure why
charset=binary
is set, but it cause error when I access S3 via API Gateway.The error message is
Charset is invalid or illegal
.When I remove
charset=binary
from Content-Type, I can access S3 repository.