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

[BUG] HTTP 404 error (Not Found) reported for unrecognized date input to API #6144

Open
elavy-harris opened this issue Mar 25, 2024 · 0 comments
Labels
bug Something isn't working

Comments

@elavy-harris
Copy link

Describe the bug
HTTP 404 error (Not Found) reported for unrecognized date input to API

To Reproduce
Steps to reproduce the behavior:

  1. Issue a command like the following: curl -X GET -su elavy -k "https://localhost:8443/api/channels/5c19b0fe-251b-40ce-a376-51e5951ba96e/messages?startDate=2020-01-01T00%3A00%3A00Z" -H X-Requested-With:whatever
  2. Observe that the response is a 404 error.

Expected behavior
A 400 error (Bad Request) is returned, preferably with information about what's bad

Actual behavior
A 404 (Not Found) error is returned.

Environment (please complete the following information):

  • OS: Docker image
  • Connect Version 4.5.0

Additional context
The API apparently requires milliseconds to be included in the date parameters and a timezone in "-0500" style. The swagger page (for all appropriate messages) should describe the required format, and the error message should at least indicate that the problem is a formatting issue with the date field.

@elavy-harris elavy-harris added the bug Something isn't working label Mar 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant