Skip to content

feature request: Enabling binary support using the API Gateway REST API #5642

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.

Sign up for GitHub

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

Jump to bottom
Closed
1 task done
calvernaz opened this issue Mar 9, 2022 · 2 comments · Fixed by #12215
Closed
1 task done

feature request: Enabling binary support using the API Gateway REST API #5642

calvernaz opened this issue Mar 9, 2022 · 2 comments · Fixed by #12215
Labels
aws:apigateway Amazon API Gateway status: confirmed Bug report was confirmed type: feature New feature, or improvement to an existing feature

Comments

@calvernaz
Copy link
Contributor

Is there an existing issue for this?

  • I have searched the existing issues

Feature description

Enabling binary support using the API Gateway REST API

https://docs.aws.amazon.com/apigateway/latest/developerguide/api-gateway-payload-encodings-configure-with-control-service-api.html

🧑‍💻 Implementation

No response

Anything else?

No response
@calvernaz calvernaz added type: feature New feature, or improvement to an existing feature aws:apigateway Amazon API Gateway labels Mar 9, 2022
@calvernaz calvernaz self-assigned this Mar 9, 2022
@localstack-bot
Copy link
Collaborator

Hello 👋! It looks like this issue hasn’t been active in longer than five months. We encourage you to check if this is still an issue in the latest release. In the absence of more information, we will be closing this issue soon. If you find that this is still a problem, please feel free to provide a comment or upvote with a reaction on the initial post to prevent automatic closure. If the issue is already closed, please feel free to open a new one.

@localstack-bot localstack-bot added the status: stale To be closed soon due to staleness label Aug 6, 2022
@localstack-bot localstack-bot added status: resolved/stale Closed due to staleness and removed status: stale To be closed soon due to staleness labels Aug 20, 2022
@thrau thrau added status: confirmed Bug report was confirmed and removed status: resolved/stale Closed due to staleness labels Aug 20, 2022
@thrau thrau reopened this Aug 20, 2022
@bentsku
Copy link
Contributor

bentsku commented Jan 29, 2025

Partially implemented for AWS_PROXY: #12199

We still need to implement full support with ContentHandling for all other integrations, for both input and output.

@bentsku bentsku linked a pull request Feb 1, 2025 that will close this issue
APIGW: binary support for non-proxy integration #12215
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
aws:apigateway Amazon API Gateway status: confirmed Bug report was confirmed type: feature New feature, or improvement to an existing feature
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

APIGW: binary support for non-proxy integration localstack/localstack
4 participants
@calvernaz @thrau @bentsku @localstack-bot