So let's get to our first demonstration.
In this example,
we're going to learn how to use online and browser tools to validate
QUIC connectivity to public or local services.
Okay, so first,
we're going to take a look at one of the online tools that
we can use to validate HTTP/3 and QUIC.
Now, one that I like to use, as I mentioned in our course materials,
I like to go to http3check.net.
There's also others out there that are available,
so you can google around and find out which one that you
like the best or works well for you.
But it's nice because you can come here to Hostname,
and all you have to do is just type in whatever it is that you're
interested in looking at as far as QUIC support.
So I'm going to go ahead and go to wireshark.org,
and I'm going to come down to CHECK.
So instantly, a report comes back,
and it shows me what this server did to go contact wireshark.org.
So this wasn't generated from my machine,
but rather from this server itself,
so the tool is based wherever this server is hosted.
From its perspective, it returns back the report,
and here, I can see a few features.
So first of all, QUIC is supported, also,
HTTP/3 is supported,
and I also can see what features and versions of QUIC are supported.
So here, I can see draft‑27, 28, and 29,
and below that, I also see that 2 connections were initiated to the server.
The first one shows me the initial connection to that server,
and then the second one shows me a 0 round‑trip time connection to this server,
so these measurements are in milliseconds.
So here,
I can see that the initial connection was actually a whole
lot faster than the second connection was.
And as we get started using QUIC and we start to see it
implemented in different environments,
that's where we should expect to see that 0‑RTT value come down to
even faster than that initial connection was.
Also, down below this,
I can see the HTTP Header information that came back from wireshark.org.
I can also, in here,
see the alternative service that was advertised from the server.
Also,
I can see the certificate that was received from that server and
do some investigation there if I so choose.
So HTTP/3 Check.
It's a great available online tool that we can use to test our services.
But let's go ahead and take a look at another example.
Let's go ahead and go to Pluralsight.
Now, here, I can see that Pluralsight, at this time of
recording, was not yet supporting HTTP/3 over QUIC.
So all that means is that I'm going to continue to support these
connections over TCP until that service becomes available.
Now, as one final test, let's go ahead and come in here, and let's go to Google,
the original QUIC supporter, and this is where I can see
QUIC is supported, as expected, HTTP/3.
But now, check out all of these QUIC versions that are available.
This is actually most of the versions in existence
that are out there in deployment.
You're going to see them by going to Google.
So how about you?
How about your company web page? Let's have you go out to HTTP/3 Check
and examine whether your site currently supports HTTP/3 over QUIC or if those connections are being done over TCP.