Kong fails to match request_path ="/" ?

[leozc]

To reproduce:

curl localhost:8001/apis
{"data":[{"upstream_url":"https://example.com/","request_path":"/api/v2","id":"YYYY","name":"api-v2","created_at":xxx}
{"data":[{"upstream_url":"https://example.com/","request_path":"/","id":"xxx","name":"","created_at":xxx}]}

curl localhost:8000
{"request_path":"/","message":"API not found with these values","request_host":["localhost"]}

However if request to:

curl localhost:8000/api/v2
this is fine.

[thibaultcha]

Yes, here you must access your API with the /api/v2 prefix path as it is the request path you chose for your API. / is not a valid request_path.

[leozc]

Arh, great, I meant to use / as a fallback value .
I think this is related to issue #847

[thibaultcha]

Were you able to create an API with a request_path value of /? If so, that is not supposed to be so, there should have been an error.

[leozc]

@thibaultcha yes I am able to create an API with a request_path value of "/".

kong --version
Kong version: 0.5.4