Skip to content

Commit a62ba93

Browse files
author
Matt David
committed
Add links for RFCs
1 parent 8905c74 commit a62ba93

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

bip-http-address-service.mediawiki

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -38,19 +38,19 @@ A bitcoin wallet developer would like to use [[bip-0075.mediawiki|BIP75]] to get
3838

3939
===DANE / TLSA===
4040

41-
Address Servers SHOULD be DANE / TLSA (RFC 7671) enabled.
41+
Address Servers SHOULD be DANE / TLSA ([https://tools.ietf.org/html/rfc7671 RFC 7671]) enabled.
4242

4343
===Available Services===
4444

4545
This flow will use a HTTP OPTIONS request to the address endpoint URL in order to determine service availability. The response will use the '''Allow''' (existing) and '''Accept''' (existing) HTTP headers to inform the client which services the address endpoint supports.
4646

4747
====Allow Header Usage====
4848

49-
The '''Allow''' header is used, as defined in RFC 2616 (14.7), to supply the client with supported HTTP methods for use with the address endpoint URL. The '''Allow''' header must return supported HTTP methods for the available return MIME types. See the table below for HTTP methods that relate to supported return MIME types.
49+
The '''Allow''' header is used, as defined in [https://tools.ietf.org/html/rfc2616 RFC2616 RFC 2616] (14.7), to supply the client with supported HTTP methods for use with the address endpoint URL. The '''Allow''' header must return supported HTTP methods for the available return MIME types. See the table below for HTTP methods that relate to supported return MIME types.
5050

5151
====Accept Header Usage====
5252

53-
The '''Accept''' header is defined in RFC 2616 (14.1) and is used in the OPTIONS response. This header is generally used in the client request, but this specification uses it in the Address Service OPTIONS response.
53+
The '''Accept''' header is defined in [[https://tools.ietf.org/html/rfc2616 RFC 2616] (14.1) and is used in the OPTIONS response. This header is generally used in the client request, but this specification uses it in the Address Service OPTIONS response.
5454

5555
The '''Accept''' header MUST contain all acceptable MIME types for the endpoint. The following table defines MIME types for the appropriate return values:
5656

0 commit comments

Comments
 (0)