mirrors/bitcoin-bips
1
0
Fork 0
mirror of https://github.com/bitcoin/bips.git synced 2024-11-19 09:50:06 +01:00
Code Issues Projects Releases Wiki Activity

Merge pull request #55 from rnicoll/bip0072-http

Browse Source 
Add reference to RFC 2616 to BIP0072
This commit is contained in:
Gavin Andresen 2014-05-20 13:52:28 -04:00
commit 6bb263a26f
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
bip-0072.mediawiki
View File

@ -38,12 +38,16 @@ described in BIP 70.
Bitcoin wallets must support fetching PaymentRequests via http and Bitcoin wallets must support fetching PaymentRequests via http and
https protocols; they may support other protocols. Wallets must https protocols; they may support other protocols. Wallets must
include an Accept HTTP header in HTTP(s) requests: include an "Accept" HTTP header in HTTP(s) requests (as defined
in RFC 2616):
<pre>Accept: application/bitcoin-paymentrequest</pre> <pre>Accept: application/bitcoin-paymentrequest</pre>
If a PaymentRequest cannot be obtained (perhaps the server is If a PaymentRequest cannot be obtained (perhaps the server is
unavailable), then the customer should be informed that the merchant's unavailable), then the customer should be informed that the merchant's
payment processing system is unavailable. payment processing system is unavailable. In the case of an HTTP
request, status codes which are neither success nor error (such as
redirect) should be handled as outlined in RFC 2616.
==Compatibility== ==Compatibility==
@ -59,3 +63,7 @@ Non-backwards-compatible equivalent:
<pre> <pre>
bitcoin:?r=https://merchant.com/pay.php?h%3D2a8628fc2fbe bitcoin:?r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
</pre> </pre>
==References==
[[http://www.w3.org/Protocols/rfc2616/rfc2616.html|RFC 2616]] : Hypertext Transfer Protocol -- HTTP/1.1