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.

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

Bug: non alphanumeric path parameters cause startup failure in AWS Lambda #637

Closed
outofcoffee opened this issue Oct 2, 2024 · 1 comment · Fixed by #643
Closed

Bug: non alphanumeric path parameters cause startup failure in AWS Lambda #637

outofcoffee opened this issue Oct 2, 2024 · 1 comment · Fixed by #643
Assignees
@outofcoffee
Labels
bug

Comments

@outofcoffee
Copy link
Owner

outofcoffee commented Oct 2, 2024 •
edited
Loading

Scenario

Deployment of mock with path parameters containing non-alphanumeric characters.

Expected

Mock deployment is successful

Actual

Mock deployment fails because Lambda adapter route cannot parse unsupported path parameter characters.

Proposed approach

Need to replicate the path parameter normalisation done for Vert.x adapter.
@outofcoffee outofcoffee added the bug label Oct 2, 2024
@outofcoffee outofcoffee self-assigned this Oct 2, 2024
@outofcoffee outofcoffee linked a pull request Oct 3, 2024 that will close this issue
fix(awslambda): extends path param normalisation to all adapters. #643
Merged
@outofcoffee
Copy link
Owner Author

Fixed in #643

@outofcoffee outofcoffee mentioned this issue Oct 3, 2024
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@outofcoffee outofcoffee

Labels
bug
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

fix(awslambda): extends path param normalisation to all adapters. outofcoffee/imposter
1 participant
@outofcoffee