Skip to content

Should return 404 when path is not supported #7

Open
@sebsto

Description

@sebsto

When deploying an application that handle /myroute/{my_Params} and invoking it with GET /, it returns an HTTP 500 instead of an HTTP 404 error.

Example

openapi.yaml :

paths:
  /stocks/{symbol}:
    get:
curl -v https://mwad60wxk9.execute-api.eu-west-3.amazonaws.com/
* Host mwad60wxk9.execute-api.eu-west-3.amazonaws.com:443 was resolved.
... (redacted for brevity) ...
> GET / HTTP/2
> Host: mwad60wxk9.execute-api.eu-west-3.amazonaws.com
> User-Agent: curl/8.6.0
> Accept: */*
> 
< HTTP/2 500 
< date: Tue, 11 Jun 2024 07:58:13 GMT
< content-type: text/plain; charset=utf-8
< content-length: 53
< apigw-requestid: ZMV_Vh-tiGYEJ7Q=
< 
* Connection #0 to host mwad60wxk9.execute-api.eu-west-3.amazonaws.com left intact
There is no OpenAPI handler registered for the path /% 

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions