Skip to content

Wrong error code when sending request with bad timespan filter #496

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

Open
EHJ-52n opened this issue Mar 4, 2020 · 4 comments
Open

Wrong error code when sending request with bad timespan filter #496

EHJ-52n opened this issue Mar 4, 2020 · 4 comments

Comments

@EHJ-52n
Copy link
Member

EHJ-52n commented Mar 4, 2020

I received the wrong response code, when sending the following GET request ...api/timeseries/TBD/observations?timespan=2019-11-31/2019-12-31:

{
  "statusCode": 500,
  "reason": "Internal Server Error",
  "userMessage": "Unexpected Exception occured.",
  "developerMessage":
      "Cannot parse '2019-11-31':
       Value 31 for dayOfMonth must be in the range [1,30]"
}

The response should look like this:

{
  "statusCode": 400,
  "reason": "Bad Request",
  "userMessage":
      "timespan filter not correct: Cannot parse '2019-11-31':
       Value 31 for dayOfMonth must be in the range [1,30]",
  "developerMessage": "any additional detail, that might help."
}
@farmannaseem

This comment has been minimized.

@PavanButke

This comment has been minimized.

@thisIsChehak
Copy link

Hii @EHJ-52n I would like to work on this issue . please assign me

@ridoo
Copy link
Member

ridoo commented Apr 3, 2025

@thisIsChehak unblocked, because we treated you wrongly as kind of a bot. There are lots of requests coming in right now. Unfortunately, you re-asked for assignment on a five-years old issue. If you want to start working on it, feel free to fork this repo and play around with it. Assigning issues to random users is not how it works.

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

6 participants
@ridoo @EHJ-52n @PavanButke @farmannaseem @thisIsChehak and others