Ben Kallus

urlparse does not correctly handle signs, underscores, and whitespace in port numbers

2

# Background RFC 3986 (spec for URIs) defines a valid port string with the following grammar rule: - `port = *DIGIT` Here's the WHATWG URL spec definition: """ A URL-port...

gh-96035: Make urllib.parse.urlparse reject non-numeric ports

1

urllib.parse.urlparse uses `int` to parse port numbers, which means they can contain signs, underscores, and whitespace. This patch adds a check to ensure that only numeric port numbers parse without...

Currently, the URL parser accepts non-ASCII digits such as `'౧'` in port numbers. This is in violation of both the WHATWG URL standard and the RFCs. This patch enforces that...

Add Kestrel, the ASP.NET web server, to the Garden.

Add [Rainbows!](https://yhbt.net/rainbows/README.html) to the Garden.

Fuzzer doesn't account for the fact that Bun and Deno ignore message bodies in `GET` requests.

2

This could use a normalization

Fuzzer doesn't account for the fact that Lighttpd ignores empty header values

2

this could use a normalization

payload: `'GET / HTTP/1.1\r\nHost: b\r\nTest: \xff\r\n\r\n'`

And they should not be

Readme is too long