unofficial mirror of bug-guile@gnu.org 
 help / color / mirror / Atom feed
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: Wed, 3 Apr 2013 18:47:22 +0800	[thread overview]
Message-ID: <CAN3veRfQ_1Got94Xd+RWk+FOzy62PJFvZaStFB02Mrd+oP+Fzw@mail.gmail.com> (raw)
In-Reply-To: <87d2ubaoon.fsf@zigzag.favinet>

On 3 April 2013 18:33, Thien-Thi Nguyen <ttn@gnuvola.org> wrote:
> () Daniel Hartwig <mandyke@gmail.com>
> () Wed, 3 Apr 2013 17:47:01 +0800
>
>    Apparently we are supposed to do this a bit more and accomodate yet
>    another non-compliant service?
>
> Maybe that stuff should be exposed to the user.  Do a best effort
> conversion and if not successful, return a pair ‘(raw-string . STRING)’
> or whatever -- it's enough that it has a different type and that the
> type is documented. This way, you avoid carrying forward lots of cruft.
> Do it now before it's too late!

Interesting.  Though this does gradually erode the type barrier
erected by the web module.  I am reluctant to cede this territory.
Instead of this cruft accumulating in a few places (the web modules),
it becomes gratutiously spread around and duplicated in other
programs.

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.

>
>
>    Erk.  What is the point of defining protocols and standards then?
>
> One purpose is to challenge programmers to learn how and when to say "no".
>

:-)





  reply	other threads:[~2013-04-03 10:47 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 [this message]
     [not found]       ` <874nfnaj71.fsf@zigzag.favinet>
2013-04-04 22:45         ` Daniel Hartwig
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=CAN3veRfQ_1Got94Xd+RWk+FOzy62PJFvZaStFB02Mrd+oP+Fzw@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).