You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
URLs are defined as byte strings and have no specific encoding. The client decides how to byte-encode unicode-URLs and there is no way for the Framework to guess the encoding used by the client. It is utf8 most of the time but URLs with raw bytes in them are allowed an encodings that would break a decode('utf8') do exist.
Same goes for GET parameter. Only POST-data can be properly decoded using the "Content-Transfer-Encoding" header.
most if not all browsers will pass URLs utf-8 encoded (curl does). I shouldn't be required to decode that manually. Example:
Now call this with
curl http://localhost:8080/äöüß
. AUnicodeDecodeError
exception is raised. I can workaround this error by addingbut I don't want to ;)
The text was updated successfully, but these errors were encountered: