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

Date case sensitivity #473

Closed
mnot opened this issue Oct 12, 2020 · 5 comments · Fixed by #479
Closed

Date case sensitivity #473

mnot opened this issue Oct 12, 2020 · 5 comments · Fixed by #479

Comments

@mnot
Copy link
Member

mnot commented Oct 12, 2020

Caching 4.2:

Although all date formats are specified to be case-sensitive, a cache recipient should match day, week, and time-zone names case-insensitively.

What does "week" refer to in this text? Also, why is this separate from the text on HTTP-dates? Do we really mean that caches should parse them in a different fashion than other components?

@reschke
Copy link
Contributor

reschke commented Oct 12, 2020

...we probably should find out when and why this difference was introduced...

@bagder
Copy link

bagder commented Oct 12, 2020

Is "week" perhaps meant to be "month"?

@mnot mnot self-assigned this Oct 18, 2020
@mnot
Copy link
Member Author

mnot commented Oct 20, 2020

This appears to have been added in 7234. The obvious thing to do is to use the appropriate rule names from semantics: day-name, day-name1, month and GMT.

The relevant tests seem to support this.

It also probably makes sense to mention this relaxation in Semantics, seeing as how caches are one of the primary consumers of dates in HTTP.

@reschke
Copy link
Contributor

reschke commented Oct 20, 2020

Ok, after some digging I found: https://trac.ietf.org/trac/httpbis/ticket/165.

(so it was me :-)

@mnot
Copy link
Member Author

mnot commented Oct 21, 2020

also httpwg/httpbis-issues#165

mnot added a commit that referenced this issue Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

Successfully merging a pull request may close this issue.

3 participants