Open phrohdoh opened 5 years ago
Yeah, that seems bad 👍
Uris cannot actually contain non-ascii characters. These characters would be percent encoded.
So, tower-web could transparently percent encode these cases?
Uris cannot actually contain non-ascii characters. These characters would be percent encoded.
So, tower-web could transparently percent encode these cases?
Should this be done in the http
crate?
Filed #206 to fix the panic, although the route probably won't match due to the percent-encoding. See https://github.com/carllerche/tower-web/issues/142 and the linked thread for a wider discussion on decoding the request parameters.
This very well may be a use-case that you decide not to support but I figured I'd report it regardless.
Using
tower-web
version0.3.1
.