paivana

HTTP paywall reverse proxy
Log | Files | Refs | Submodules | README | LICENSE

commit 8d8fa9eff8035be218e77b76e2f5b98f70ca3b1c
parent 73b2170520dfbd70416755ad0d1171bb435b80fd
Author: Christian Grothoff <christian@grothoff.org>
Date:   Sun, 31 May 2026 12:56:41 +0200

use 409, not 400

Diffstat:
MREADME | 5+++--
Msrc/backend/paivana-httpd_pay.c | 2+-
2 files changed, 4 insertions(+), 3 deletions(-)

diff --git a/README b/README @@ -18,8 +18,9 @@ How it works expression which determines the set of pages the template applies to. 1. An HTTP client accesses a page at `paivana-httpd`. 2. If the paywall is enabled for the respective URL and no valid access - cookie is present, `paivana-httpd` renders a static paywall HTML page - (customizable Mustache template) referencing the payment template. + cookie is present, `paivana-httpd` redirects the browser to + a static paywall HTML page (customizable Mustache template) + referencing the payment template. The page includes a "Paivana" HTTP header to also facilitate agentic payments. 3. The browser computes a unique payment identifier and diff --git a/src/backend/paivana-httpd_pay.c b/src/backend/paivana-httpd_pay.c @@ -249,7 +249,7 @@ order_status_cb (struct PayRequest *ph, GNUNET_break_op (0); ph->response = TALER_MHD_make_error (TALER_EC_PAIVANA_PAYMENT_MISSING, ph->order_id); - ph->response_status = MHD_HTTP_BAD_REQUEST; + ph->response_status = MHD_HTTP_CONFLICT; } else {