From: Eric Wong <email@example.com> To: firstname.lastname@example.org Subject: HTTP::Date replacing Date::Parse [was: TODO: remove done items, add some more] Date: Sun, 3 Nov 2019 09:02:42 +0000 Message-ID: <20191103090242.GA28983@dcvr> (raw) In-Reply-To: <email@example.com> > +* consider using HTTP::Date instead of Date::Parse, since we need the > + former is capable of parsing RFC822-ish dates, used by Plack, and > + the latter is missing from OpenBSD and maybe other distros. Ugh, HTTP::Date will try to use Time::Zone under the hood if available for non-conformant dates. And Time::Zone is part of the same TimeDate package as Date::Parse, which I was trying to stop depending on... At least one incompatibility I've found is the inability of HTTP::Date to handle the "+1" (yes, single digit) timezone offset which we have a test case for in t/msgtime.t There's probably a few more wacky historical cases which we lack test cases for. Hell, there's even a case of 3-digit years in LKML history which we special-case for. So, I'm not sure it's worth it... The good thing is that going forward, dates seem to much more conformant as clients got better. So there's only a finite set of historical special cases which we'd need to deal with.
prev parent reply index Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top 2019-07-13 21:54 [PATCH] TODO: remove done items, add some more Eric Wong 2019-11-03 9:02 ` Eric Wong [this message]
Reply instructions: You may reply publically to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style List information: http://public-inbox.org/README * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to=20191103090242.GA28983@dcvr \ --firstname.lastname@example.org \ --email@example.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: link
user/dev discussion of public-inbox itself Archives are clonable: git clone --mirror http://public-inbox.org/meta git clone --mirror http://czquwvybam4bgbro.onion/meta git clone --mirror http://hjrcffqmbrq6wope.onion/meta git clone --mirror http://ou63pmih66umazou.onion/meta Example config snippet for mirrors Newsgroups are available over NNTP: nntp://news.public-inbox.org/inbox.comp.mail.public-inbox.meta nntp://ou63pmih66umazou.onion/inbox.comp.mail.public-inbox.meta nntp://czquwvybam4bgbro.onion/inbox.comp.mail.public-inbox.meta nntp://hjrcffqmbrq6wope.onion/inbox.comp.mail.public-inbox.meta nntp://news.gmane.org/gmane.mail.public-inbox.general note: .onion URLs require Tor: https://www.torproject.org/ AGPL code for this site: git clone https://public-inbox.org/public-inbox.git