Skip to content

Commit 3e89e8b

Browse files
author
Matt David
committed
Remove whitespace causing empty grey boxes
1 parent faec02c commit 3e89e8b

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

bip-http-address-service.mediawiki

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,7 +43,7 @@ Address Servers SHOULD be DANE / TLSA ([https://tools.ietf.org/html/rfc7671 RFC
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.
46-
46+
4747
====Allow Header Usage====
4848

4949
The '''Allow''' header is used, as defined in [https://tools.ietf.org/html/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.
@@ -103,7 +103,7 @@ The HTTP POST request MUST set the '''Content-Transfer-Encoding''' header to "bi
103103
====Immediate Response====
104104

105105
The Address Service MUST respond with a HTTP Status Code of '''200 (OK)''' if the response type is a ProtocolMessage or EncryptedProtocolMessage. The Address Service MUST respond with a ProtocolMessage or EncryptedProtocolMessage based on the '''Accept''' header in the client request.
106-
106+
107107
====Delayed Response====
108108

109109
The Address Service MUST respond with a HTTP Status Code of '''202 (Accepted)''' and the '''Location''' header set to a location to later retrieve the resulting ProtocolMessage or EncryptedProtocolMessage

0 commit comments

Comments
 (0)