From f077dd7fd0211ffb79d02318fe7601e13d34dc42 Mon Sep 17 00:00:00 2001
From: clawbot <35+clawbot@noreply.example.org>
Date: Wed, 11 Nov 2026 07:50:59 +0100
Subject: [PATCH] Say that rproxy passes a refused question's 400 to the
 visitor (closes #326)

The comment above `readQuestion` in `internal/waf/waf.go` said `rproxy` treats a refused question (`400`, no disposition) as no answer. It passes the `400` to the visitor, and `SWRP_DEFAULT_DISPOSITION` does not apply, as `SPEC.md` and `internal/rproxy/waf.go` say. Comment only.

Model: opus-5-5
---
 internal/waf/waf.go | 8 ++++----
 1 file changed, 4 insertions(+), 4 deletions(-)

diff --git a/internal/waf/waf.go b/internal/waf/waf.go
index 9d5ed66..d624946 100644
--- a/internal/waf/waf.go
+++ b/internal/waf/waf.go
@@ -213,10 +213,10 @@ func (h *handler) answerQuestion(w http.ResponseWriter, r *http.Request) {
 
 // readQuestion returns the visitor's address and the body a question carries,
 // and whether waf takes the question. It answers a question it does not
-// take with 400 and no disposition, which rproxy treats as it treats no
-// answer. The id of a question it takes is held from here on, without a
-// decision yet, so that another question with that id is refused while this
-// one is being handled.
+// take with 400 and no disposition. rproxy passes that 400 to the visitor,
+// and SWRP_DEFAULT_DISPOSITION does not apply. The id of a question waf takes
+// is held from here on, without a decision yet, so that another question with
+// that id is refused while this one is being handled.
 //
 // The body is read before any check, since Go's server does not send an answer
 // until it has read the body. A question whose body stops arriving gets no