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

Restore landing page #111

Merged
merged 5 commits into from
Jan 9, 2023
Merged

Restore landing page #111

merged 5 commits into from
Jan 9, 2023

Commits on Dec 22, 2022

  1. Fix error response

    The `error` field is not valid for an API Gateway response. As noted in the AWS docs below, when an error response contains invalid fields, it will always return a `502` error code with a body of `{"message": "Internal server error"}`. This PR updates the error response fields to contain valid fields and a more sensible response message.
    
    - https://docs.aws.amazon.com/lambda/latest/dg/services-apigateway.html#services-apigateway-errors
    ajschmidt8 committed Dec 22, 2022
    Configuration menu
    Copy the full SHA
    33c654c View commit details
    Browse the repository at this point in the history
  2. rm try/catch block

    ajschmidt8 committed Dec 22, 2022
    Configuration menu
    Copy the full SHA
    193136b View commit details
    Browse the repository at this point in the history
  3. use JSON.stringify()

    ajschmidt8 committed Dec 22, 2022
    Configuration menu
    Copy the full SHA
    70dcf4d View commit details
    Browse the repository at this point in the history
  4. Configuration menu
    Copy the full SHA
    f56bf47 View commit details
    Browse the repository at this point in the history
  5. rm dead link

    ajschmidt8 committed Dec 22, 2022
    Configuration menu
    Copy the full SHA
    291cc5a View commit details
    Browse the repository at this point in the history