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.

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

Properly work out RFC2822 support #200

Open
ariebovenberg opened this issue Jan 15, 2025 · 1 comment
Open

Properly work out RFC2822 support #200

ariebovenberg opened this issue Jan 15, 2025 · 1 comment
Labels
discussion Discussion is needed before proceeding enhancement New feature or request

Comments

@ariebovenberg
Copy link
Owner

Currently, formatting and parsing RFC2822 timestamps is possible, but it uses a function from the standard library that doesn't technically validate—and probably isn't spec compliant either.

That said, the spec of RFC2822 has some strange edge cases (e.g. BurntSushi/jiff#39) so the limits of the implementation would need to be carefully considered.
@ariebovenberg ariebovenberg added enhancement New feature or request discussion Discussion is needed before proceeding labels Jan 15, 2025
@BurntSushi
Copy link

Yeah so far the limitation in Jiff's parser seems to be working out fine. Jiff's RFC 2822 parser is used in uv. I'm not quite sure how much variation uv sees in HTTP servers, but it was varied enough to demand explicit RFC 9110 support for printing.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
discussion Discussion is needed before proceeding enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@BurntSushi @ariebovenberg