raw_path should not be Optional

[nggit]

The reason raw_path is purely what the client sends, it's not ambiguous.

While path tends to have various assumptions, whether %2f should be decoded or not, percent-encoding contains utf-8 or what, is it true that decoding by forcing utf-8 is guaranteed valid or not? etc.

Applications are better off relying on raw_path to avoid the unpredictable consequences, bugs, etc. if they rely on path.

Also, I find this reasoning is nonsensical:

Some web server implementations may be unable to provide this

https://asgi.readthedocs.io/en/latest/specs/www.html#http-connection-scope

[carltongibson]

The history here is on #87.

[Kludex]

In the typing module, it's actually bytes:

asgiref/asgiref/typing.py

Line 73 in f587b12

raw_path: bytes

Also, the type in the spec should be Optional[byte string].

---

I have my own interpretation of the types in Uvicorn: https://github.com/Kludex/uvicorn/blob/9b1c6c45ed7fe8bd485ddad475f0feff03971af7/uvicorn/_types.py#L63, which I agreed with raw_path being just bytes.