Ambigous datetime values are accepted but should be rejected #365

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.

Sign up for GitHub

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

Jump to bottom

Closed

philvarner opened this issue Mar 1, 2022 · 1 comment

Assignees

Labels

spec

Collaborator

philvarner commented Mar 1, 2022

These two datetime values are accepted for query, but are not valid RFC 3339 datetimes, and should be rejected with a 400.

Search with datetime=1937-01-01T12:00:27.87+0100 returned status code 200 instead of 400 -- no colon between hour and minute in tz
Search with datetime=1985-12-12T23:20:50.52 returned status code 200 instead of 400 -- no timezone

philvarner added the spec label

philvarner self-assigned this

philvarner mentioned this issue

Improve RFC 3339 datetime handling #368

Merged

4 tasks

Collaborator

geospatial-jeff commented Aug 4, 2022

Closed with #368

geospatial-jeff closed this as completed

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment