20k per hour is more than reasonable for well-behaved clients, no? why are we being so permissive?
Logs: rproxy writes one short line per request (status, bytes, times, servewaf's answer, and whether the default gave it); servewaf one detailed line per decision. The request id joins…
Once the answer has ended, rproxy reports its status, bytes and times to servewaf, which counts the bytes toward the byte limits and adds the request to the client's history. The visitor does…
no. query strings get logged verbatim. why wouldn't we want the exact queries logged? secrets go in POST data. query strings are assumed to be logged.
per-minute should be 300-500, no?
the full query strings should be logged, that's correct.
200-300 per minute max seems reasonable, no?
there absolutely needs to be a per-minute limit.
I think that the first 64k of request bodies should go to the waf.
I envision a live request viewer functionality backend in the waf that allows for an admin to review inbound traffic and…
Replace. Also while we will use the inherited container setup, most people will run the rproxy in a separate container from the app, so in the usual case it will be 3 containers.
Non-issue.
Whenever and wherever possible, node and yarn and npm and python and the Python installer tools that are bundled with it should be installed from the distribution. And we don't need to worry about…
