taler-docs

Documentation for GNU Taler components, APIs and protocols
Log | Files | Refs | README | LICENSE

commit 3a7f174743237ab82c8b38875c853d1409795662
parent b00e168425c7c0a34e4ad8fd6d20eb3d1439c28f
Author: Christian Grothoff <christian@grothoff.org>
Date:   Tue, 19 May 2026 10:14:32 +0200

disambiguate SITE

Diffstat:
Mdesign-documents/076-paywall-proxy.rst | 7++++---
1 file changed, 4 insertions(+), 3 deletions(-)

diff --git a/design-documents/076-paywall-proxy.rst b/design-documents/076-paywall-proxy.rst @@ -58,12 +58,13 @@ Steps: * If such a cookie is set and valid, the request is reverse-proxied to upstream. *Stop.* * Otherwise, an HTTP 302 Redirect to - ``/.well-known/paivana/templates/$ID#SITE`` + ``/.well-known/paivana/templates/$ID#$WEBSITE`` is returned. Here, ``$ID`` is the template ID and - ``$SITE`` is the website currently being visited. This way, + ``$WEBSITE`` is base64url-encoding of the full URL of + the website currently being visited. This way, the template page can be fully static and cached, and the JavaScript logic on that page can learn which website - to pay for (and after payment go back there). + to pay for (and after payment redirect the browser there). * When the browser requests ``/.well-known/paivana/templates/$ID`` a static **cachable** paywall page is returned,