[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#14128: web/http.scm: bad-header date check (UTC?)
From: |
Daniel Hartwig |
Subject: |
bug#14128: web/http.scm: bad-header date check (UTC?) |
Date: |
Fri, 5 Apr 2013 06:45:15 +0800 |
On 3 April 2013 20:32, Thien-Thi Nguyen <address@hidden> wrote:
> () Daniel Hartwig <address@hidden>
> () 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!’.
bug#14128: web/http.scm: bad-header date check (UTC?), Andy Wingo, 2013/04/04