commit 8fb2ca4050e743b8afa4a4a5b8d81d9e4a07a656 parent ac374fef4646cad330747dc3ddebbc8ab6bc7471 Author: Christian Grothoff <christian@grothoff.org> Date: Sun, 23 Jun 2024 10:03:58 +0200 fix #8970 Diffstat:
| M | core/tos.rst | | | 14 | +++++++++++++- |
1 file changed, 13 insertions(+), 1 deletion(-)
diff --git a/core/tos.rst b/core/tos.rst @@ -28,11 +28,23 @@ and the privacy policy of a service. instead prompt the user again at the next opportunity. This is usually only the case if the terms of service were not configured correctly. + The "Etag" is generated from the first 256 bits of the SHA-512 hash + over the terms and encoded in Crockford base-32. However, this behavior + is not normative and clients MUST NOT rely on it. + + A "Taler-Terms-Version" header is generated to indicate the **legal** version + of the terms. This header will change whenever something **legally** changed + in the terms of service and the user must review and accept the terms of + service again. If the "Taler-Terms-Version" is identical to one that the + user has already accepted, there is no need for the user to review the terms + again. + When returning a full response (not a "304 Not Modified"), the server should also include a "Avail-Languages" header which includes a comma-separated list of the languages in which the terms of service are available in (see `availability hints specification - <https://datatracker.ietf.org/doc/draft-nottingham-http-availability-hints/>`_). Clients can use this to generate a language switcher + <https://datatracker.ietf.org/doc/draft-nottingham-http-availability-hints/>`_). + Clients can use this to generate a language switcher for users that may not have expressed a proper language preference. **Response:**