Runtime: Remove the Trailing Slash from URI when converting to String

[mjd575]

In Asp.net core 3.1, I create a Uri like below:

Uri uri = new Uri($"https://www.example.com?id=1&name=aa");

When I convert it to string:

uri.ToString()

It will automatically add a trailing slash behind the domain:

https://www.example.com/?id=1&name=aa

Is there a way to remove the trailing slash?

[msftbot[bot]]

Tagging subscribers to this area: @dotnet/ncl
See info in area-owners.md if you want to be subscribed.

[karelz]

Try uri.OriginalString:

```c#
Uri uri = new Uri($"https://www.example.com?id=1&name=aa");
Console.WriteLine(uri.ToString());
Console.WriteLine(uri.AbsoluteUri);
Console.WriteLine(uri.OriginalString);

Output:

https://www.example.com/?id=1&name=aa
https://www.example.com/?id=1&name=aa
https://www.example.com?id=1&name=aa
```

[MihaZupan]

What is the goal behind removing this slash?

[mjd575]

I'm just curious why this slash is automatically added, seems it is the default behavior.

[karelz]

@mjd575 I believe the slash is required by the Uri RFC. Without slash, it is not well formed IMO -- @MihaZupan will be able to say for sure.

[MihaZupan]

I believe it may have been required by ancient Url specifications, though not required by the current spec. So having the slash there can theoretically improve compatibility.

Chrome will for example add slash when making a request. See http://example.com?foo=bar

I don't see any value in omitting it - is there a use-case behind it, or just curiosity?

[KalleOlaviNiemitalo]

Omitting the slash could make sense for distinguishing an OPTIONS * request (RFC 7230 §5.3.4) from OPTIONS /, as hinted by the URI normalization rule (RFC 7230 §2.7.3). HttpConnection.SendAsyncCore in SocketsHttpHandler does not seem to support that, though.