HTTPRequest.path does not preserve percent-escaping

[jeffska]

Because of the code path utilizing the (now deprecated) URL.path var, the resulting path in HTTPRequest is not percent-escaped. Normally that may not be a big issue, but that also means that any %2F values are getting unescaped to '/' which then messes with the actual segments.

My use case can't use predefined routes exclusively, so I end up having to inspect the path. The vast majority of the time it's not going to be an issue, but there are a few rare edge cases where it could be.

[swhitty]

Would you suggest adding an additional property for unescaped paths?

Or I could an option to HTTPServer.Configuration to preserve unescape paths for all HTTPRequest received.

(Configuration option may be easier as it sidesteps breaking changes to public API)

[jeffska]

My preference would be an additional property w/ an array of escaped path segments. But otherwise, any way to preserve the unescaped path would be helpful.

Oh, and thanks by the way. Between FlyingFox and your backwards-compatible Mutex, you've solved two of my issues with the app I'm working on.

[swhitty]

OK, what do you think about adding a new property to HTTPRequest that can represent the raw request target as per RFC9112 ?

// /a%2Fb?q=1
public var target: String 

[jeffska]

That's better than nothing. But it would be nice not to have to parse out the query manually.