From: Daniel Hartwig <mandyke@gmail.com>
To: Thien-Thi Nguyen <ttn@gnuvola.org>
Cc: aconchillo@gmail.com, 14128@debbugs.gnu.org
Subject: bug#14128: web/http.scm: bad-header date check (UTC?)
Date: Fri, 5 Apr 2013 06:45:15 +0800 [thread overview]
Message-ID: <CAN3veRcR5oG5CqKUgBQD+sc1g0v8NsOnc3J55jMuDo2m6g+8ag@mail.gmail.com> (raw)
In-Reply-To: <874nfnaj71.fsf@zigzag.favinet>
On 3 April 2013 20:32, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Daniel Hartwig <mandyke@gmail.com>
> () Wed, 3 Apr 2013 18:47:22 +0800
>
> Interesting. Though this does gradually erode the type barrier
> erected by the web module. I am reluctant to cede this territory.
>
> I suppose playing whack-a-mole is fun sometimes, for a while.
>
> Instead of this cruft accumulating in a few places (the web modules),
> it becomes gratutiously spread around and duplicated in other
> programs.
>
> Well more precisely, in those programs which talk to such servers, and
> actually care about that particular data. (Many programs do not.)
>
> It was previously suggested to implement a permissive flag that,
> while not passing unparsed data to the users, will at least not raise
> errors and stop.
>
> In this direction, you might as well go higher-order. Client code
> specifies the conversion procedure, and there is a reasonable default
> (also exported, so that the user can compose it w/ their own bad-input
> detection/handling). This is more Schemely, in my mind.
That is ‘declare-header!’.
next prev parent reply other threads:[~2013-04-04 22:45 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-03 7:59 bug#14128: web/http.scm: bad-header date check (UTC?) Aleix Conchillo Flaqué
2013-04-03 9:47 ` Daniel Hartwig
2013-04-03 10:33 ` Thien-Thi Nguyen
2013-04-03 10:47 ` Daniel Hartwig
[not found] ` <874nfnaj71.fsf@zigzag.favinet>
2013-04-04 22:45 ` Daniel Hartwig [this message]
2013-04-03 12:34 ` Ludovic Courtès
2013-04-03 14:57 ` Aleix Conchillo Flaqué
2013-04-03 15:02 ` Aleix Conchillo Flaqué
2013-04-04 21:01 ` Andy Wingo
2013-11-19 8:35 ` Mark H Weaver
Reply instructions:
You may reply publicly 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: https://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CAN3veRcR5oG5CqKUgBQD+sc1g0v8NsOnc3J55jMuDo2m6g+8ag@mail.gmail.com \
--to=mandyke@gmail.com \
--cc=14128@debbugs.gnu.org \
--cc=aconchillo@gmail.com \
--cc=ttn@gnuvola.org \
/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
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).