public inbox for bitcoindev@googlegroups.com
 help / color / mirror / Atom feed
From: Andy Alness <andy@coinbase.com>
To: bitcoin-development@lists.sourceforge.net
Subject: [Bitcoin-development] Allow cross-site requests of payment requests
Date: Sun, 11 May 2014 18:05:20 -0700	[thread overview]
Message-ID: <CALKy-wq6FZs39KX-gk2PizEEikLvHhxMkt=OT61fcUchsaLpfg@mail.gmail.com> (raw)

[-- Attachment #1: Type: text/plain, Size: 565 bytes --]

Would it be a terrible idea to amend BIP 70 to suggest implementors include
a "Access-Control-Allow-Origin: *" response header for their payment
request responses? I don't think this opens up any useful attack vectors.

I ask because this would make it practical for pure HTML5 web wallets to
use the payment protocol entirely in-browser. Without this I think it would
be necessary for the server hosting the wallet's HTML to fetch payment
requests on the browser's behalf. This is somewhat inelegant and has
security/resource implications for the back-end.

-Andy

[-- Attachment #2: Type: text/html, Size: 687 bytes --]

             reply	other threads:[~2014-05-12  1:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-05-12  1:05 Andy Alness [this message]
2014-05-12 10:28 ` [Bitcoin-development] Allow cross-site requests of payment requests Mike Hearn
2014-05-12 17:21   ` Andy Alness

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='CALKy-wq6FZs39KX-gk2PizEEikLvHhxMkt=OT61fcUchsaLpfg@mail.gmail.com' \
    --to=andy@coinbase.com \
    --cc=bitcoin-development@lists.sourceforge.net \
    /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