01a02ecf - Unlisted forwards belong to the upstream backend - #14
01a02ecf - Unlisted forwards belong to the upstream backend#14TaprootFreak wants to merge 4 commits into
Conversation
|
EN: Ready after 4 review passes. DetailsPass 1: pin the REVIEW/CONTRIBUTING ownership sentences (they were missing). Rejected, not counted: a block parser instead of the repo's existing one-line |
A route this process does not list and therefore forwards belongs to the upstream HTTP backend. Forwarding it does not make it a listed route.
Grep pins now lock the process bullet, both README sentences, and the REVIEW fail rule so unlisted forwards stay upstream endpoints.
Rewrap the CONTRIBUTING, README, and REVIEW ownership clauses onto single lines so grep pins lock the complete wording, not a prefix.
The ownership grep now matches the complete unlisted-traffic sentence, not only the bold suffix.
f59517a to
b3a6b90
Compare
|
EN: Ready after 5 review passes. DetailsPass 1: pin REVIEW/CONTRIBUTING ownership sentences. Rejected, not counted:
Rebased onto develop after #13 ( |
EN:
Unlisted traffic this process forwards is not an endpoint of this process; it belongs to the upstream HTTP backend.
DE:
Ungelisteter Traffic, den dieser Prozess weiterleitet, ist kein Endpoint dieses Prozesses; er gehoert zum Upstream-HTTP-Backend.
Details
Listed routes stay finished here and must never be forwarded. Unknown routes stay unnamed. Forwarding an unknown route does not make it a listed route.
test/test-server.shpins the process bullet in CONTRIBUTING.md, both README sentences, and the REVIEW.md fail rule so that wording cannot drop while a weaker paragraph remains.