From d3d1f242fd13527137f01310458132c5a324e79a Mon Sep 17 00:00:00 2001 From: Ross Nicoll Date: Sat, 26 Apr 2014 17:34:03 +0100 Subject: [PATCH 1/2] Added reference to RFC 2616 to BIP0072. --- bip-0072.mediawiki | 8 +++++++- 1 file changed, 7 insertions(+), 1 deletion(-) diff --git a/bip-0072.mediawiki b/bip-0072.mediawiki index dae53f46..e4ed52f3 100644 --- a/bip-0072.mediawiki +++ b/bip-0072.mediawiki @@ -38,7 +38,9 @@ described in BIP 70. Bitcoin wallets must support fetching PaymentRequests via http and 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): + 
Accept: application/bitcoin-paymentrequest
If a PaymentRequest cannot be obtained (perhaps the server is @@ -59,3 +61,7 @@ Non-backwards-compatible equivalent: 
 bitcoin:?r=https://merchant.com/pay.php?h%3D2a8628fc2fbe
+ +==References== + +[[http://www.w3.org/Protocols/rfc2616/rfc2616.html|RFC 2616]] : Hypertext Transfer Protocol -- HTTP/1.1 \ No newline at end of file From e91d87919bf3cce6d0dcd5c5bf1960c65129c0a5 Mon Sep 17 00:00:00 2001 From: Ross Nicoll Date: Sat, 26 Apr 2014 17:39:26 +0100 Subject: [PATCH 2/2] Added note about handling HTTP statuses which are neither error nor success. --- bip-0072.mediawiki | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/bip-0072.mediawiki b/bip-0072.mediawiki index e4ed52f3..8617dbe4 100644 --- a/bip-0072.mediawiki +++ b/bip-0072.mediawiki @@ -45,7 +45,9 @@ in RFC 2616): If a PaymentRequest cannot be obtained (perhaps the server is 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==