Skip to content

Example code for AWS S3 issue that results in empty metadata when using aws-chunked encoding

License

Notifications You must be signed in to change notification settings

mgajda/aws-empty-content-encoding-issue

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

3 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

aws-empty-content-encoding-issue

This illustrates issue #537 and #536 with Amazonka and S3 API.

brendanhay/amazonka#537 brendanhay/amazonka#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).

About

Example code for AWS S3 issue that results in empty metadata when using aws-chunked encoding

Topics

Resources

License

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published