SseServerTransport should better handle the quoting the post message endpoint.

[pradeepvishwakarma]

Just pointing out the issue where it malformed the endpoint url. Can we send full endpoint instead of passing the route as some sse integration requires full endpoints.

>> sse.py -> SseServerTransport -> connect_sse

from urllib.parse import quote
from uuid import uuid4

session_id = uuid4()
root_path = "https://example.com/api_prefix"
full_message_path_for_client = root_path.rstrip("/") + "/messages"
client_post_uri_data = (
f"{quote(full_message_path_for_client)}?session_id={session_id.hex}"
)
print(client_post_uri_data)

Output : https%3A//example.com/api_prefix/messages?session_id=0bb8b48cc4d1447c992e6872f2668b05
Expected : https://example.com/api_prefix/messages?session_id=0bb8b48cc4d1447c992e6872f2668b05

[AishwaryaKalloli]

Hi, I am trying to understand the problem, I understood how to fix the issue related to % symbol.
However, I was curious about how this scenario would be triggered where we would have the full_url including "https://example.com".

As per my understanding so far, client_post_uri_data would resolve to "/api_prefix/messages?session_id=0bb8b48cc4d1447c992e6872f2668b05" because scope("root_path") would be "/api_prefix".

If you could give an example of how this scenario is triggered it would be helpful.

[AishwaryaKalloli]

To add details:
The client appends the original url to the server's endpoint event. This allows for more secure connection.