commit 942a9a6ea080b81fc6b8d32682737b5c3820aa52 parent fc21aca668ba5a67885d44a3877eaf87272415e4 Author: Christian Grothoff <christian@grothoff.org> Date: Sun, 3 May 2026 09:00:09 +0200 discuss alternatives Diffstat:
| M | design-documents/076-paywall-proxy.rst | | | 7 | +++++++ |
1 file changed, 7 insertions(+), 0 deletions(-)
diff --git a/design-documents/076-paywall-proxy.rst b/design-documents/076-paywall-proxy.rst @@ -152,6 +152,13 @@ Alternatives * Do not re-use the session ID mechanism but introduce some new concept. This has the drawback of us needing additional tables and indicies, and also the existing use of the session ID is very parallel to this one. +* Instead of doing a 302 Redirect, cache control could have been achieved by + specifying a "Vary: Cookie" HTTP header. We may combine these and use + that to additionally enable caching of the 302 Redirect. The 302 solution + has the advantage that there is only one page to cache per template, and + the disadvantage of an additional redirect. Note that this is purely + a frontend design choice, wallets and merchant backends work nicely with + either approach. Drawbacks =========