Teknium 8986981df4 security(gateway): set explicit client_max_size on 3 uncapped aiohttp servers (#59180) ... Sibling sweep from the #58902 raft review found aiohttp servers still running on the implicit 1 MiB default with no explicit body cap: - bluebubbles webhook (127.0.0.1): 1 MiB explicit cap — events are small JSON/form payloads; attachments arrive via the REST API - teams Bot Framework listener (0.0.0.0 bind — most exposed): 1 MiB cap; activities are JSON well under that - hermes proxy server: 10 MB cap mirroring api_server's MAX_REQUEST_BYTES (chat-completion payloads can be large, but must stay bounded) client_max_size bounds every read path including chunked transfer-encoding requests that carry no Content-Length (#58536/#58902 pattern). Deliberately excluded: feishu, whatsapp_cloud, sms, line, wecom, msgraph — open contributor PRs (#54938, #54944, #54620, #54931, #54934, #25296) already cover those; reviewing them separately preserves their credit. 3 regression tests pin the wiring.		2026-07-05 14:48:28 -07:00
..
__init__.py	feat(teams): add Microsoft Teams platform adapter as a plugin	2026-04-30 01:19:34 -07:00
adapter.py	security(gateway): set explicit client_max_size on 3 uncapped aiohttp servers (#59180)	2026-07-05 14:48:28 -07:00
plugin.yaml	refactor(plugins/platforms): migrate IRC + Teams to new env_enablement + cron_deliver hooks	2026-05-07 07:15:44 -07:00