sneak/smallwebwaf
1
0 Fork 0
Code Issues 12 Pull Requests 2 Actions Packages Projects Releases Wiki Activity

README: what rproxy gives an app without the decider #386

New Issue
Closed
opened 2026-11-14 17:35:56 +01:00 by clawbot · 1 comment
clawbot commented 2026-11-14 17:35:56 +01:00
Collaborator
Copy link
Copy source

sneak, chat, 14 November 2026:

> the readme should also have a paragraph about the benefits rproxy has without the decider; things like timeouts and header size limits and general http request correctness

Task

Add one paragraph to README.md saying what rproxy gives an app on its own, with no WAF answering (the decider unset or down): its request timeouts, its request and response size limits, its header size and count limits, and its rejection of malformed HTTP requests. State only what the code at the head of next does, with the default for each limit. Put it where a reader deciding whether to run rproxy will find it.

Definition of done

  • One paragraph (a short bulleted list inside it is fine) in README.md; every claim matches the code on next.
  • The prose meets the README rules: one idea per sentence, plain words, a list of things as a bulleted list.
  • make check passes. One PR into next.

Model: opus-5-5

sneak, chat, 14 November 2026: > the readme should also have a paragraph about the benefits rproxy has without the decider; things like timeouts and header size limits and general http request correctness ## Task Add one paragraph to `README.md` saying what `rproxy` gives an app on its own, with no WAF answering (the decider unset or down): its request timeouts, its request and response size limits, its header size and count limits, and its rejection of malformed HTTP requests. State only what the code at the head of `next` does, with the default for each limit. Put it where a reader deciding whether to run `rproxy` will find it. ## Definition of done - One paragraph (a short bulleted list inside it is fine) in `README.md`; every claim matches the code on `next`. - The prose meets the README rules: one idea per sentence, plain words, a list of things as a bulleted list. - `make check` passes. One PR into `next`. Model: opus-5-5
clawbot commented 2026-11-14 17:40:11 +01:00
Author
Collaborator
Copy link
Copy source

PR: #389, branch issue-386-readme-rproxy-alone.

I added one paragraph to the README's "What it does" section, with a bulleted list. It covers what rproxy refuses and limits on its own, each with its default.

Deviation: rproxy has no limit on the number of headers, so the paragraph says the header-count and header-line limits belong to waf.

Model: opus-5-5

PR: https://git.eeqj.de/sneak/smallwebwaf/pulls/389, branch `issue-386-readme-rproxy-alone`. I added one paragraph to the README's "What it does" section, with a bulleted list. It covers what `rproxy` refuses and limits on its own, each with its default. Deviation: `rproxy` has no limit on the number of headers, so the paragraph says the header-count and header-line limits belong to `waf`. Model: opus-5-5
Sign in to join this conversation.
No Branch/Tag Specified
Labels
Clear labels
critical
Extremely important: data loss, a security hole, production down, or basic use impossible
 merge-ready
Reviewed and ready for the owner to merge
 needs-checks
Checks must be fixed before review
 needs-decision
Waits on an owner decision
 needs-decision
Waiting on a decision by the owner
 needs-decision
needs-rebase
Conflicts with next; rebase required
 needs-review
Review not yet done
 needs-rework
Review found issues to fix
 post-1.0
red-next
No labels
Milestone
No items
No Milestone
Projects
Clear projects
No projects
Assignees
Clear assignees
clawbot sneak (Jeffrey Paul)
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sneak/smallwebwaf#386