Clarify raw_path Definition for WebSockets Protocol in the Specification

[raptium]

The definition of raw_path in the ASGI specification differs slightly between HTTP and WebSockets protocols.

• HTTP: The specification explicitly states that the query string is excluded from raw_path.

asgiref/specs/www.rst

Lines 107 to 110 in b7aaa79

	* ``raw_path`` (*byte string*) -- The original HTTP path component,
	excluding any query string, unmodified from the bytes that were
	received by the web server. Some web server implementations may
	be unable to provide this. Optional; if missing defaults to ``None``.

• WebSockets: The specification does not mention whether the query string should be included or excluded from raw_path.

asgiref/specs/www.rst

Lines 318 to 321 in b7aaa79

	* ``raw_path`` (*byte string*) -- The original HTTP path component
	unmodified from the bytes that were received by the web server. Some
	web server implementations may be unable to provide this. Optional;
	if missing defaults to ``None``.

To ensure clarity and consistency, it would be beneficial to explicitly define the behavior of raw_path for WebSockets:

1. If the query string should be excluded: The specification should use the same wording as in the HTTP section to avoid ambiguity.
2. If the query string should be included: This should be explicitly stated, along with any rationale for the differing behavior.

Given the potential for confusion, it would be helpful to clarify this in the specification.

[Kludex]

Yeah, having this difference looks a bit weird. Do you remember if it was intentional? @andrewgodwin

[andrewgodwin]

I do not believe that was intentional - my guess is that we specifically clarified it for standard HTTP but not for WebSocket. I would say we should update the WebSocket side to say that it also excludes the query string.

[Kludex]

@raptium Would you like to send a PR here?

[Kludex]

We can close this @andrewgodwin 🙏