Support different POST content types #10
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Ignore .idea
Add option to supply desired content type to use in fetch(). Some AWS services don't support JSON in POST requests but expect raw form data.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
By default, POST data is formatted as JSON. Not all AWS services accept JSON though, in our example, Amazon SES. I used the existing
optionsparameter to supply a different content type (in this caseapplication/x-www-form-urlencoded) and format / hash the payload accordingly.GET requests in UrlFetchApp are limited to 2kB so by using a POST instead we can send requests up to 50MB:
AWS.request('email', 'eu-west-1', 'SendEmail', undefined, 'POST', payload, undefined, undefined, {contentType: 'application/x-www-form-urlencoded'});