Code4IT

The place for .NET enthusiasts, Azure lovers, and backend developers

C# Tip: use the Ping class instead of an HttpClient to ping an endpoint

2021-10-19 2 min read CSharp Tips
Just a second! 🫷
If you are here, it means that you are a software developer. So, you know that storage, networking, and domain management have a cost .

If you want to support this blog, please ensure that you have disabled the adblocker for this site. I configured Google AdSense to show as few ADS as possible - I don't want to bother you with lots of ads, but I still need to add some to pay for the resources for my site.

Thank you for your understanding.
- Davide

What if you wanted to see if a remote website is up and running?

Probably, the first thing that may come to your mind is to use a common C# class: HttpClient. But it may cause you some trouble.

There is another way to ping an endpoint: using the Ping class.

Why not using HttpClient

Say that you need to know if the host at code4it.dev is live. With HttpClient you might use something like this:

async Task Main()
{
    var url = "https://code4it.dev";

    var isUp = await IsWebsiteUp_Get(url);

    Console.WriteLine("The website is {0}", isUp ? "up" : "down");
}

private async Task<bool> IsWebsiteUp_Get(string url)
{
    var httpClient = new HttpClient(); // yes, I know, I should use HttpClientFactory!
    var httpResponse = await httpClient.GetAsync(url);
    return httpResponse.IsSuccessStatusCode;
}

There are some possible issues with this approach: what if there is no resource available in the root? You will have to define a specific path. And what happens if the defined resource is under authentication? IsWebsiteUp_Get will always return false. Even when the site is correctly up.

Also, it is possible that the endpoint does not accept HttpGet requests. So, we can use HttpHead instead:

private async Task<bool> IsWebsiteUp_Head(string url)
{
    var httpClient = new HttpClient();
    HttpRequestMessage request = new HttpRequestMessage
    {
        RequestUri = new Uri(url),
        Method = HttpMethod.Head // Not GET, but HEAD
    };
    var result = await httpClient.SendAsync(request);
    return result.IsSuccessStatusCode;
}

We have the same issues described before, but at least we are not bound to a specific HTTP verb.

By the way, we need to find another way.

How to use Ping

By using the Ping class, we can get rid of those checks and evaluate the status of the Host, not of a specific resource.

private async Task<bool> IsWebsiteUp_Ping(string url)
{
    Ping ping = new Ping();
    var hostName = new Uri(url).Host;

    PingReply result = await ping.SendPingAsync(hostName);
    return result.Status == IPStatus.Success;
}

The Ping class comes in the System.Net.NetworkInformation namespace, and allows you to perform the same operations of the ping command you usually send via command line.

Conclusion

We’ve seen why you should use Ping instead of HttpClient to perform a ping-like operation.

There’s more than this: head to this more complete article to learn more.

πŸ‘‰ Let’s discuss it on Twitter or on the comment section below.

🐧

About the author

Davide Bellone is a Principal Backend Developer with more than 10 years of professional experience with Microsoft platforms and frameworks.

He loves learning new things and sharing these learnings with others: that’s why he writes on this blog and is involved as speaker at tech conferences.

He's a Microsoft MVP πŸ†, conference speaker (here's his Sessionize Profile) and content creator on LinkedIn.