Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ensure literal/primitive response bodies are correctly handled #226

Merged
merged 9 commits into from
Sep 18, 2015

Conversation

brendanhay
Copy link
Owner

Extends amazonka-gen with a json literal type, that can be added via annex / config overrides. This allows for fixes with S3's GetObjectPolicy, Lambda, and Glacier operations that return non-streaming response bodies that are in factor opaque JSON documents.

Fixes #224.

@brendanhay brendanhay force-pushed the feature/issue-224 branch 2 times, most recently from d9ec7e6 to 486cf5d Compare September 17, 2015 09:39
@brendanhay
Copy link
Owner Author

Looks like PutBucketPolicy is also incorrect.

Additionally defaults non-streaming payload literal bodies
to JSON objects, which assumes that the top-level response
is always an object and not a list per the JSON spec.
brendanhay added a commit that referenced this pull request Sep 18, 2015
Ensure literal/primitive response bodies are correctly handled
@brendanhay brendanhay merged commit 567a232 into develop Sep 18, 2015
@brendanhay brendanhay deleted the feature/issue-224 branch September 18, 2015 07:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

S3 GetBucketPolicy returns Json
1 participant