Exact

Exact Union RegExp

Devon Hudson 8b0083cad9 Respond with useful error codes when Content-Length header/s are invalid (#19212) ... Related to https://github.com/element-hq/synapse/issues/17035, when Synapse receives a request that is larger than the maximum size allowed, it aborts the connection without ever sending back a HTTP response. I dug into our usage of twisted and how best to try and report such an error and this is what I came up with. It would be ideal to be able to report the status from within `handleContentChunk` but that is called too early on in the twisted http handling code, before things have been setup enough to be able to properly write a response. I tested this change out locally (both with C-S and S-S apis) and they do receive a 413 response now in addition to the connection being closed. Hopefully this will aid in being able to quickly detect when https://github.com/element-hq/synapse/issues/17035 is occurring as the current situation makes it very hard to narrow things down to that specific issue without making a lot of assumptions. This PR also responds with more meaningful error codes now in the case of: - multiple `Content-Length` headers - invalid `Content-Length` header value - request content size being larger than the `Content-Length` value ### Pull Request Checklist <!-- Please read https://element-hq.github.io/synapse/latest/development/contributing_guide.html before submitting your pull request --> * [X] Pull request is based on the develop branch * [X] Pull request includes a [changelog file](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#changelog). The entry should: - Be a short description of your change which makes sense to users. "Fixed a bug that prevented receiving messages from other servers." instead of "Moved X method from `EventStore` to `EventWorkerStore`.". - Use markdown where necessary, mostly for `code blocks`. - End with either a period (.) or an exclamation mark (!). - Start with a capital letter. - Feel free to credit yourself, by adding a sentence "Contributed by @github_username." or "Contributed by [Your Name]." to the end of the entry. * [X] [Code style](https://element-hq.github.io/synapse/latest/code_style.html) is correct (run the [linters](https://element-hq.github.io/synapse/latest/development/contributing_guide.html#run-the-linters)) --------- Co-authored-by: Eric Eastwood <erice@element.io>		2025-12-08 21:39:18 +00:00
..
federation	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
server	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
__init__.py	Use type hinting generics in standard collections (#19046)	2025-10-22 16:48:19 -05:00
ca.crt	Tests for SSL certs for federation connections	2019-06-10 16:14:20 +01:00
ca.key	Tests for SSL certs for federation connections	2019-06-10 16:14:20 +01:00
server.key	Tests for SSL certs for federation connections	2019-06-10 16:14:20 +01:00
test_additional_resource.py	Update license headers	2023-11-21 15:29:58 -05:00
test_client.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
test_endpoint.py	Update license headers	2023-11-21 15:29:58 -05:00
test_matrixfederationclient.py	Move reading of multipart response into try body (#19062)	2025-10-30 15:22:52 +00:00
test_proxy.py	Use type hinting generics in standard collections (#19046)	2025-10-22 16:48:19 -05:00
test_proxyagent.py	Write union types as X | Y where possible (#19111)	2025-11-06 14:02:33 -06:00
test_servlet.py	Port Clock functions to use Duration class (#19229)	2025-12-01 13:55:06 +00:00
test_simple_client.py	Introduce Clock.call_when_running(...) to include logcontext by default (#18944)	2025-09-22 10:27:59 -05:00
test_site.py	Respond with useful error codes when Content-Length header/s are invalid (#19212)	2025-12-08 21:39:18 +00:00