CORS.toHttpRoutes and CORS.toHttpApp are unconfigurable
See original GitHub issueBoth of them should take a CORSConfig
parameter. We should deprecate the versions that don’t, starting in 0.22.
Issue Analytics
- State:
- Created 2 years ago
- Reactions:1
- Comments:11 (11 by maintainers)
Top Results From Across the Web
Configuring CORS for an HTTP API - Amazon API Gateway
To support unauthorized OPTIONS requests, add an OPTIONS /{proxy+} route to your API that doesn't require authorization and attach an integration to the...
Read more >How to handle CORS | CORS - Amazon HTTP API p9 - YouTube
Welcome to part 9 of the new tutorial series on Amazon HTTP API. In this video, we will cover how to handle CORS...
Read more >How do I resolve a CORS error for my API Gateway REST API?
We appreciate your feedback: https://amazonintna.qualtrics.com/jfe/form/SV_a5xC6bFzTcMv35sSkip directly to the demo: 0:40For more details ...
Read more >API Gateway HTTP + Lambda integration not enabling CORS
I have an API Gateway with an HTTP API + route that utilizes a Lambda function integration. From the AWS documentation, I see...
Read more >API Gateway HTTP API CORS - Stack Overflow
For anyone using HTTP API and the proxy route ANY /{proxy+}. You will need to explicitly define your route methods in order for...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Okay, thanks for the advice Ross , will keep in mind next time, I will make those changes and submit the PR
When will the PR get reviewed ? will you be reviewing it @rossabaker ?