[API Proposal]: ReadOnlySpan<char> based overload for Uri.CheckHostName

Open
#110,615 3 comments 3 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
35/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Stale
Tech stack
csharp

Research direction

Start at the existing Uri.CheckHostName(string?) entry point and review how its hostname validation is exposed. Compare the proposed ReadOnlySpan overload with the existing behavior and API usage; done means the proposal is implemented with equivalent hostname classification and validation for spans.

Written by the indexing model from the issue text.

Description

api-suggestion area-System.Net
Background and motivation

This method wraps some useful checks that can determine both the type and validity of hostnames. When checking the validity of the hostname part of a larger string part of a path or url string (such as the hostname portion of a UNC path), it could be useful to perform this check on just a ReadOnly<char> slice. Recreating to avoid the allocation would be annoying when the method already exists.

API Proposal
namespace System;

public class Uri : ISpanFormattable, ISerializable
{
     public static UriHostNameType CheckHostName(string? name);
+    public static UriHostNameType CheckHostName(ReadOnlySpan<char> name)
}
API Usage
string uncPath = @"\\192.168.0.1\someShare";
int hostnameEnd = uncPath[2..].IndexOf('\\') + 2;
ReadOnlySpan<char> hostNameSpan = uncPath.AsSpan()[2..hostnameEnd];
UriHostNameType hostNameType = Uri.CheckHostName(hostNameSpan);
Alternative Designs

More comprehensive parsing/validation tools for string paths could be introduced.

Risks

Slightly larger API surface.

Dominant language
C#
Stars
18.3k
Forks
5.6k
PR merge metrics
PR metrics pending

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from dotnet/runtime

All issues in dotnet/runtime

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.