Allow non-percent-encoded spaces in path

[WhyNotHugo]

The space character is not a reserved character. While it MAY be used in percent-encoded form, this is not mandatory and it is acceptable to use raw spaces in URL paths.

Add Space (0x20) to the list of characters that don't need to be percent-encoded.

[seanmonstar]

I don't see any feasible way this could work, at least for HTTP/1. Parsers assume (because the spec defines this) that the request line is 3 tokens separate by spaces. A parser would be upset to see GET /hello world HTTP/1.1.

Note RFC 9112 3.2:

No whitespace is allowed in the request-target. Unfortunately, some user agents fail to properly encode or exclude whitespace found in hypertext references, resulting in those disallowed characters being sent as the request-target in a malformed request-line.

[WhyNotHugo]

You’re right, this won’t work. Thanks for pointing me in the right direction. Aside from a space character, is there any other non-reserved URL character that needs to be escaped?

[WhyNotHugo]

I'm working on WebDAV, where URLs are sometimes specified in the request header, and sometimes inside an XML in the body. I've been using the same Uri type for both, but it seems that rules for percent-encoding the URIs inside the XML body are more relaxed.

Should I just use a separate type for those?