From fcc6eb20d73e992bb64861ed01b91c13419984f3 Mon Sep 17 00:00:00 2001 From: Julian Reschke Date: Sun, 16 Feb 2025 19:36:09 +0100 Subject: [PATCH] query: new Examples Section - indirect --- draft-ietf-httpbis-safe-method-w-body.xml | 28 ++++++++++++++++++++++- 1 file changed, 27 insertions(+), 1 deletion(-) diff --git a/draft-ietf-httpbis-safe-method-w-body.xml b/draft-ietf-httpbis-safe-method-w-body.xml index dbfa38ab9..47ada1731 100644 --- a/draft-ietf-httpbis-safe-method-w-body.xml +++ b/draft-ietf-httpbis-safe-method-w-body.xml @@ -617,7 +617,7 @@ Allow: GET, QUERY, OPTIONS, HEAD -
+
The Content-Location and Location response fields provide a way to identify alternate resources that will respond to GET requests, either for the received result of the request, or for future @@ -720,6 +720,32 @@ Date: Sun, 17 November 2024, 16:13:17 GMT the original QUERY request in order to obtain a new alternative location.
+ +
+ + Servers can send "indirect" responses using the status code 303 ("See Other", + ). + + + Given the request at the beginning of , + a server might respond with: + + +HTTP/1.1 303 See Other +Content-Type: text/plain +Date: Sun, 17 November 2024, 16:13:17 GMT +Location: /contacts/stored-queries/42 + +See stored query at "/contacts/stored-queries/42". + + + This is similar to including Location on a direct response, except that no result + for the query is returned. This allows the server to only generate an alternative + resource. This resource could then be used as shown in + . + +
+