-
Notifications
You must be signed in to change notification settings - Fork 82
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
Support for API Gateway with a custom domain #16
Comments
Can you provide an example of your API gateway request JSON when using a custom domain? |
@graemerocher the main difference is the
where |
@musketyr So it is my understanding that is what the Or am I mistaken? |
that could be one of the solutions but it would be better if the integration is able to determine it itself. the API can be in theory accessed in both ways - using the custom domain and using the original AWS native URL. here's a sample JSON:
|
FYI here's a sample request handler to inspect the request
my library uses |
When using the API Gateway support added in micronaut-projects/micronaut-core#540 it works until you add a custom domain name to the API Gateway, then the Lambda is invoked but return a 404.
Steps to Reproduce
Not sure how I can add a easy to reproduce test case since some setup for the domain is needed.
Expected Behaviour
Same output as the generated API Gateway URL should be given
Actual Behaviour
Tell us what happens instead
The Lambda is invoked but a HTTP 404 is generated.
Environment Information
The text was updated successfully, but these errors were encountered: