PRD 0041: Git HTTP request bounds #144
Reference in New Issue
Block a user
Delete Branch "prd-0041-git-http-request-bounds"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Closes #138.
PRD: https://gitea.dideric.is/didericis/bot-bottle/src/branch/prd-0041-git-http-request-bounds/docs/prds/0041-git-http-request-bounds.md
Summary
ValueErroron Content-Length parse and return HTTP 400 for missing or non-numeric valuessupervise_server.py)Changes (1 commit)
docs/prds/0041-git-http-request-bounds.md— add PRD 0041 (Draft)@@ -20,2 +20,4 @@DEFAULT_PORT = 9420# Body-size cap matching supervise_server.py's 1 MiB limit._MAX_BODY_BYTES = 1 * 1024 * 1024If the agent committed an image to the repo greater than 1 MiB, would it now fail? That's probably fine/good, and assets shouldn't be in a git repo generally, but could see this potentially being annoying for people if seo
@@ -20,2 +20,4 @@DEFAULT_PORT = 9420# Body-size cap matching supervise_server.py's 1 MiB limit._MAX_BODY_BYTES = 1 * 1024 * 1024Yes — a push whose packfile body exceeds 1 MiB would 413. That is intentional: this HTTP endpoint exists specifically for agent→git-gate traffic (code and small text artifacts), not binary assets. 1 MiB matches the existing cap in
supervise_server.pyso the two channels are consistently bounded.If it does become a pain point,
_MAX_BODY_BYTESis a named constant and trivial to raise, but I would not widen it preemptively.e84e7e6ba4to71005d56e2