From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from sog-mx-3.v43.ch3.sourceforge.com ([172.29.43.193] helo=mx.sourceforge.net) by sfs-ml-3.v29.ch3.sourceforge.com with esmtp (Exim 4.76) (envelope-from ) id 1VEUkO-00085P-KJ for bitcoin-development@lists.sourceforge.net; Wed, 28 Aug 2013 01:40:36 +0000 Received-SPF: pass (sog-mx-3.v43.ch3.sourceforge.com: domain of gmail.com designates 209.85.212.177 as permitted sender) client-ip=209.85.212.177; envelope-from=gavinandresen@gmail.com; helo=mail-wi0-f177.google.com; Received: from mail-wi0-f177.google.com ([209.85.212.177]) by sog-mx-3.v43.ch3.sourceforge.com with esmtps (TLSv1:RC4-SHA:128) (Exim 4.76) id 1VEUkN-0007kY-JD for bitcoin-development@lists.sourceforge.net; Wed, 28 Aug 2013 01:40:36 +0000 Received: by mail-wi0-f177.google.com with SMTP id hi5so651894wib.16 for ; Tue, 27 Aug 2013 18:40:29 -0700 (PDT) MIME-Version: 1.0 X-Received: by 10.180.183.108 with SMTP id el12mr13580846wic.55.1377654028946; Tue, 27 Aug 2013 18:40:28 -0700 (PDT) Received: by 10.194.156.163 with HTTP; Tue, 27 Aug 2013 18:40:28 -0700 (PDT) Date: Wed, 28 Aug 2013 11:40:28 +1000 Message-ID: From: Gavin Andresen To: Bitcoin Dev Content-Type: multipart/alternative; boundary=001a11c353ac04d21a04e4f8139c X-Spam-Score: -0.6 (/) X-Spam-Report: Spam Filtering performed by mx.sourceforge.net. See http://spamassassin.org/tag/ for more details. -1.5 SPF_CHECK_PASS SPF reports sender host as permitted sender for sender-domain 0.0 FREEMAIL_FROM Sender email is commonly abused enduser mail provider (gavinandresen[at]gmail.com) -0.0 SPF_PASS SPF: sender matches SPF record 1.0 HTML_MESSAGE BODY: HTML included in message -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature X-Headers-End: 1VEUkN-0007kY-JD Subject: [Bitcoin-development] BIP 72 updated: require Accept HTTP header X-BeenThere: bitcoin-development@lists.sourceforge.net X-Mailman-Version: 2.1.9 Precedence: list List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Wed, 28 Aug 2013 01:40:36 -0000 --001a11c353ac04d21a04e4f8139c Content-Type: text/plain; charset=ISO-8859-1 I just added a requirement to the BIP 72 (bitcoin: URI payment protocol) spec: Wallets must include an Accept HTTP header in HTTP requests: Accept: application/bitcoin-paymentrequest ... and submitted a pull request so the reference implementation follows the spec. Thanks to Stephen/Jeff at BitPay for the suggestion. I'll make a similar change to BIP 70 and require wallets set Accept: application/bitcoin-paymentrequestack when sending the Payment and expecting a PaymentACK message in return. -- -- Gavin Andresen --001a11c353ac04d21a04e4f8139c Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: quoted-printable
I just added a requirement to the BIP 72 (bitcoin: URI pay= ment protocol) spec:

Wallets must include an Accept HTTP header in HTTP requests:

Accept: application/bitcoin-paymentrequest
... and submitted a pu= ll request so the reference implementation follows the spec.

=
Thanks to Stephen/Jeff at BitPay for the suggestion. I'll ma= ke a similar change to BIP 70 and require wallets set Accept: application/b= itcoin-paymentrequestack when sending the Payment and expecting a PaymentAC= K message in return.

--
--
Gavin Andresen
--001a11c353ac04d21a04e4f8139c--