Okay, so now let's look at another demo,
only we're going to look at the developer tools within Chrome this time
and see how we can test QUIC with those features.
So to do that, I'm first going to go up to the top right.
This is my Chrome browser.
I'm going to select my little three dots, which give me my different options.
Then I come down to More Tools, and at the bottom of that,
I can see Developer Tools.
That's one way that I can activate these tools.
And what you'll notice on the bottom half of my screen,
now I have this toolset that's going to allow me to
see things like network connections, performance,
memory, security,
so a lot of the different features are built into the developer tools.
So if you've never used this before,
it's actually interesting to start to poke through and
see what kind of things you can find.
Now, presently, I can see my red button over there.
I am recording, so this means that the next site that I go to,
I'm going to start to see some things come in.
So let's go ahead and come up here.
I'm just going to go to wireshark.org, and I'm going to hit Enter there,
and this is where I can see as Wireshark,
this page starts to populate.
I can see all the activity that I have down below.
Now, for right now,
I'm just going to come over here to my red button and stop recording for now.
Now, a couple of things for you.
First, I just want to make sure that you know that I'm on the Network tab.
So let's come over there,
and that'll let us see the network‑based connections down below.
Also, I have activated the Protocol column down below.
All we do to do that, just right‑click,
and I want to make sure that you check Protocol,
and then that will show you the actual h2 or h3 draft 29 connection
version that's being made to whatever that server is.
So I'm going to go all the way up to the top,
and let's take a look first at our initial connection to wireshark.org.
That was actually made over http/1.1.
Well, right there on its heels, the next one that I see was over h2,
and a little bit further down,
I can see that some of these queries were actually made over HTTP/3 draft 29.
So just with a glance,
I can see that this server supports and the client is
actually using HTTP/3 over QUIC.
Now, if I want to examine this just a little bit further,
this is where I can come over and just select that connection,
and this will bring me to the header values for that Request URL,
Request Method, and this is where I can come down in my response headers,
and I can see the different QUIC versions that were advertised by the server.
Now, this might look familiar from what we saw at the packet level in Wireshark,
but the nice thing about this is we don't have to capture and
import those TLS keys in order to decrypt it.
Here, we can see it almost real time.
Now, by default,
the client is going to do the most recent one that it also can support.
And in this case, that's h3‑29.
Now, there's a whole lot more that we can dig into with the developer tools.
This is a really interesting part of this browser.
We have our waterfall over here on the right.
We have our response time.
We even have our indicator up on top,
and we can dig in a little bit further into a specific period of time
and see what was going on at that period of time.
If I click and drag over a specific period of time,
it'll zoom in there,
and it'll show me just those connections that were active at that point in time.
So there's a really rich toolset that we can use in the developer tools.
And when it comes to QUIC, this is just a fast way that we can determine,
does a server support it, what's the version, and how long is it taking to connect?