Skip to content

Commit

Permalink
BIP 72: Reduce the amount of escaping needed
Browse files Browse the repository at this point in the history
RFC 3986 obsoletes RFC 1738, which this BIP was wrongly referencing.
The new RFC requires far less escaping for query parameters.
  • Loading branch information
swansontec committed Mar 7, 2014
1 parent c823eeb commit 8207368
Showing 1 changed file with 5 additions and 4 deletions.
9 changes: 5 additions & 4 deletions bip-0072.mediawiki
Original file line number Diff line number Diff line change
Expand Up @@ -22,8 +22,9 @@ bitcoin wallets.

The bitcoin: URI scheme is extended with an additional, optional
"r" parameter, whose value is a URL from which a PaymentRequest
message should be fetched (unsafe and reserved octets in the URL value
must be encoded as described in RFC 1738).
message should be fetched (characters not allowed within the scope
of a query parameter must be percent-encoded as described in RFC 3986
and bip-0021).

If the "r" parameter is provided and backwards compatibility
is not required, then the bitcoin address portion of the URI may be
Expand Down Expand Up @@ -52,9 +53,9 @@ r parameter and will initiate a payment to bitcoin address.
==Examples==
A backwards-compatible request:
<pre>
bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
bitcoin:mq7se9wy2egettFxPbmn99cK8v5AFq55Lx?amount=0.11&r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
</pre>
Non-backwards-compatible equivalent:
<pre>
bitcoin:?r=https%3A%2F%2Fmerchant.com%2Fpay.php%3Fh%3D2a8628fc2fbe
bitcoin:?r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
</pre>

0 comments on commit 8207368

Please sign in to comment.