diff options
| -rw-r--r-- | bip-http-address-service.mediawiki | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/bip-http-address-service.mediawiki b/bip-http-address-service.mediawiki index 2701dfd..0c61a73 100644 --- a/bip-http-address-service.mediawiki +++ b/bip-http-address-service.mediawiki @@ -43,7 +43,7 @@ Address Servers SHOULD be DANE / TLSA ([https://tools.ietf.org/html/rfc7671 RFC ===Available Services=== 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. - + ====Allow Header Usage==== 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 ====Immediate Response==== 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. - + ====Delayed Response==== 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 |