rproxy: the package doc says a refusal gets a page of its own
It said every answer from waf but allow goes to the visitor as waf gave it, which a 403 or 429 refusal no longer does. Model: opus-5-5
This commit is contained in:
1 parent
354e10ea60
commit
a7f25f0558
1 file changed
+2
-1
@@ -1,7 +1,8 @@
|
||||
// Package rproxy is the reverse proxy in front of one app that asks waf
|
||||
// about each request. It passes a request waf allows to the app and the
|
||||
// app's answer back, within the size and time limits. Any other answer from
|
||||
// waf goes to the visitor as waf gave it.
|
||||
// waf goes to the visitor as waf gave it, except that a refusal of 403 or 429
|
||||
// has a page of rproxy's own as its body.
|
||||
// SWW_RPROXY_WAF_BACKEND_NO_ANSWER_DISPOSITION decides only when waf cannot
|
||||
// be connected to, does not answer at all, or does not answer within
|
||||
// SWW_RPROXY_WAF_BACKEND_TIMEOUT_MS, or while the circuit breaker for asks to
|
||||
|
||||
Reference in new issue
Block a user