From: Gavin Andresen <gavinandresen@gmail•com>
To: Bitcoin Dev <bitcoin-development@lists•sourceforge.net>
Subject: [Bitcoin-development] BIP 72 updated: require Accept HTTP header
Date: Wed, 28 Aug 2013 11:40:28 +1000 [thread overview]
Message-ID: <CABsx9T1WD5de-pWH2AsdWYi2RnZ-+upbeFEn4es8H3M3wo_bzw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 524 bytes --]
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
[-- Attachment #2: Type: text/html, Size: 930 bytes --]
reply other threads:[~2013-08-28 1:40 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=CABsx9T1WD5de-pWH2AsdWYi2RnZ-+upbeFEn4es8H3M3wo_bzw@mail.gmail.com \
--to=gavinandresen@gmail$(echo .)com \
--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