Note: 10.199.3.44 is my virtual server with HTTP/2 profile applied. ![]() The packet capture taken below was the result of the following curl command issued from my ubuntu Linux client (I could've used a browser instead): Confirmation of which protocol will be used I'll just issue a HEAD request and later on a GET request and we'll see how it looks like on Wireshark.įor more info about HTTP/2 profile and HTTP/2 protocol itself you can read the article I published on AskF5 and Jason's DevCentral article: What is HTTP Part X - HTTP/2. ![]() It's a simple test and here's the topology: ![]() It turns out Wireshark is a perfect tool for me to do just that. Some people find it easier to do a "test drive" first to learn how a new protocol works in its simplest form and only then read the RFC.
0 Comments
Leave a Reply. |