You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We are incorrectly matching URIs to the spec when the URI has a prefix
that is not in the spec.
This is because when generating the regex describing the spec, we're not
using the `^` anchor to match from the beginning of the text.
Fixes#1483.
We are incorrectly matching URIs to the spec when the URI has a prefix
that is not in the spec.
This is because when generating the regex describing the spec, we're not
using the `^` anchor to match from the beginning of the text.
Fixes#1483.
I discovered this while testing integration with Lambda behind API Gateway, where the deployed API contains the API stage in the URI:
Both these cases fail:
The text was updated successfully, but these errors were encountered: