https://github.com/mgajda/aws-empty-content-encoding-issue
Example code for AWS S3 issue that results in empty metadata when using aws-chunked encoding
https://github.com/mgajda/aws-empty-content-encoding-issue
aws-s3 content-encoding issue
Last synced: 8 months ago
JSON representation
Example code for AWS S3 issue that results in empty metadata when using aws-chunked encoding
- Host: GitHub
- URL: https://github.com/mgajda/aws-empty-content-encoding-issue
- Owner: mgajda
- License: bsd-3-clause
- Created: 2019-08-02T16:19:17.000Z (almost 7 years ago)
- Default Branch: master
- Last Pushed: 2019-08-14T03:57:13.000Z (almost 7 years ago)
- Last Synced: 2025-10-10T01:34:48.260Z (8 months ago)
- Topics: aws-s3, content-encoding, issue
- Language: Haskell
- Size: 97.7 KB
- Stars: 0
- Watchers: 1
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.html
- Changelog: ChangeLog.md
- License: LICENSE
Awesome Lists containing this project
README
aws-empty-content-encoding-issue
This illustrates issue #537 and #536 with Amazonka and S3 API.
https://github.com/brendanhay/amazonka/issues/537 https://github.com/brendanhay/amazonka/issues/536
Installation
This should suffice to replicate issue: 1. Install Haskell Stack: curl -sSL https://get.haskellstack.org/ | sh 2. git clone https://github.com/mgajda/aws-empty-content-encoding-issue.git 3. cd aws-empty-content-encoding-issue 4. stack build 5. stack run
Check that metadata for the new file is Content-Encoding: (empty string).