From: Andreas Schildbach <andreas@schildbach•de>
To: bitcoin-development@lists•sourceforge.net
Subject: Re: [Bitcoin-development] BIP 21 (modification BIP 20)
Date: Tue, 31 Jan 2012 12:55:01 +0100 [thread overview]
Message-ID: <jg8kql$bct$1@dough.gmane.org> (raw)
In-Reply-To: <CA+s+GJAvEPda7UGHDoz84OavSh5jdN8wOhGgrNUgPU_Wh66Xyw@mail.gmail.com>
On 01/31/2012 11:22 AM, Wladimir wrote:
> To ensure forward compatibility with optional fields, we need to define
> how a client handles fields that it doesn't know about.
>
> When should it display an error message, and when should it silently
> accept and ignore the extraneous fields?
IMHO its standard that unknown URL parameters are simply ignored. I
think we should not change this principle.
> (For example, if something that restricts the validity, such
> as "expires" is added later on, it is pretty important not to ignore it.
> Older clients should refuse to comply.)
In this case, you'd need to refuse *all* parameters you don't know
about. In consequence, all extensions would break older clients.
next prev parent reply other threads:[~2012-01-31 11:55 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-29 23:55 Amir Taaki
2012-01-30 9:13 ` Wladimir
2012-01-31 8:23 ` Andreas Schildbach
2012-01-31 8:35 ` Wladimir
2012-01-31 10:01 ` Gary Rowe
2012-01-31 10:22 ` Wladimir
2012-01-31 11:55 ` Andreas Schildbach [this message]
2012-01-31 12:03 ` Wladimir
2012-01-31 10:44 ` Pieter Wuille
2012-01-30 18:07 thomasV1
2012-01-30 18:44 ` Luke-Jr
2012-01-30 18:50 Gary Rowe
2012-01-30 18:56 ` Luke-Jr
2012-01-30 19:13 ` Gary Rowe
2012-01-30 19:17 ` Luke-Jr
2012-01-31 6:54 ` thomasV1
2012-01-31 13:12 ` Gavin Andresen
2012-01-31 13:20 ` Cameron Garnham
2012-01-31 10:39 [Bitcoin-development] BIP 21 (modification BIP 20)] Pieter Wuille
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='jg8kql$bct$1@dough.gmane.org' \
--to=andreas@schildbach$(echo .)de \
--cc=bitcoin-development@lists$(echo .)sourceforge.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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