taler-docs

commit 158c72b4ee0c705fbcebd8f59cd5c504f68b379b
parent ed016cb3cf6c7f02f3b149db61b0c90d6c5c296d
Author: Martin Schanzenbach <schanzen@gnunet.org>
Date:   Thu, 22 Oct 2026 13:36:01 +0200

Clarify the taldir registration return of Location headers

Diffstat:
M
core/taldir/post-register-ALIASTYPE.rst
 | 
4
++++

1 file changed, 4 insertions(+), 0 deletions(-)
diff --git a/core/taldir/post-register-ALIASTYPE.rst b/core/taldir/post-register-ALIASTYPE.rst
@@ -41,6 +41,10 @@
   :http:statuscode:`202 Accepted`
      Registration was initiated, the client should check for receiving
      a challenge at the alias where registration was attempted.
+     Some alias types may require other web-based verifications.
+     In such cases (e.g. OAuth2-based verifications) this response will
+     include a `Location`-header that must be followed in order to
+     complete the verification.
   :http:statuscode:`402 Payment Required`
      Client needs to make a Taler payment before proceeding. See
      standard Taler payment procedure.