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

Return specific status code when route not found #144

Closed
kontrollanten opened this issue Mar 6, 2018 · 1 comment
Closed

Return specific status code when route not found #144

kontrollanten opened this issue Mar 6, 2018 · 1 comment
Assignees
Milestone

Comments

@kontrollanten
Copy link

Current behavior:
When a route isn't found, a 500 HTTP status is returned with the following response

{
  "error":{
    "code":2099,
    "message":"Connection between locations not found"
  },
  "info":{
    "engine":{
      "version":"4.5.0",
      "build_date":"2018-02-27T14:22:36Z"
    },
    "timestamp":1520362248836
  }
}

Expected behavior
A 404 HTTP status code, or eventually an unique error code (not 2099, which is Unknown error).

According to this test case, it seems that it's by design:

// Option 1 signifies that the route should not cross any borders

Is there any reason it is implemented like this?

Thanks!

@MichaelsJP MichaelsJP removed their assignment Mar 13, 2018
@rabidllama rabidllama added this to the 4.5.1 milestone Mar 13, 2018
@rabidllama
Copy link
Contributor

Code has been updated so that a 2009 internal error code is returned with a 404 http response

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants