Skip to content

Allow updated_at to be an epoch string - #165

Open
multun wants to merge 1 commit into
ramosbugs:mainfrom
multun:updated-at-string
Open

multun wants to merge 1 commit into
ramosbugs:mainfrom
multun:updated-at-string

Conversation

@multun

@multun multun commented Apr 24, 2024

Copy link
Copy Markdown
Contributor

Allow unix timestamps within a string for updated_at, as follows:
"updated_at": "1713964430.299453"

This is not allowed by the specification, but was observed in the wild on at least one OpenAM
instance. This misbehavior is probably caused by a plugin or unusual config, as other OpenAM
instances work just fine.

Instance owners were notified, and aren't willing to do anything about it.

This parsing leniancy feature is gated behind "accept-string-epoch".

@multun
multun force-pushed the updated-at-string branch from c107ff5 to 375812e Compare April 25, 2024 09:35
Allow unix timestamps within a string for updated_at, as follows:
  "updated_at": "1713964430.299453"

This is not allowed by the specification, but was observed in the wild on at least one OpenAM
instance. This misbehavior is probably caused by a plugin.

This parsing leniancy feature is gated behind "accept-string-epoch".
@multun
multun force-pushed the updated-at-string branch from 375812e to 964d84b Compare April 25, 2024 09:37
@multun multun changed the title Allow updated_at to be a number within a string Allow updated_at to be an epoch string Apr 25, 2024
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

Successfully merging this pull request may close these issues.

1 participant