How is Wireshark constructing HTTP Flows?
I'm trying to understand how Wireshark knows what request is correlated to a response - "Follow HTTP Flow".
For example, some http packets may be sent with gaps of other tcp packets.
Some have responses that are separated between several tcp packets and Wireshark needs to understand they are correlated.
Does this have to do with SEQ and ACK in TCP?
networking tcp wireshark
asked Jan 24 at 18:34
funerrfunerr
127116
add a comment |
I'm trying to understand how Wireshark knows what request is correlated to a response - "Follow HTTP Flow".
For example, some http packets may be sent with gaps of other tcp packets.
Some have responses that are separated between several tcp packets and Wireshark needs to understand they are correlated.
Does this have to do with SEQ and ACK in TCP?
networking tcp wireshark
asked Jan 24 at 18:34
funerrfunerr
127116
add a comment |
I'm trying to understand how Wireshark knows what request is correlated to a response - "Follow HTTP Flow".
For example, some http packets may be sent with gaps of other tcp packets.
Some have responses that are separated between several tcp packets and Wireshark needs to understand they are correlated.
Does this have to do with SEQ and ACK in TCP?
networking tcp wireshark
asked Jan 24 at 18:34
funerrfunerr
127116
I'm trying to understand how Wireshark knows what request is correlated to a response - "Follow HTTP Flow".
For example, some http packets may be sent with gaps of other tcp packets.
Some have responses that are separated between several tcp packets and Wireshark needs to understand they are correlated.
Does this have to do with SEQ and ACK in TCP?
networking tcp wireshark
networking tcp wireshark
asked Jan 24 at 18:34
funerrfunerr
127116
asked Jan 24 at 18:34
funerrfunerr
127116
asked Jan 24 at 18:34
funerrfunerr
127116
asked Jan 24 at 18:34
funerrfunerr
127116
asked Jan 24 at 18:34
funerrfunerr
127116
127116
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Does this have to do with SEQ and ACK in TCP?
Yes, HTTP/2 and earlier all rely on TCP for keeping track of the packet stream, and TCP uses Seq and Ack numbers for this, along with the 4-tuple of (source IP, source port, destination IP, destination port).
HTTP/2 has additional flow-tracking mechanisms of top of TCP (that HTTP 1.1 and earlier didn't have) because HTTP/2 allows multiple concurrent HTTP transactions within a single TCP stream.
HTTP/3 (the new name for QUIC) is a different story, because it is UDP-based. But I believe it uses a TCP-like Seq/Ack mechanism to keep things straight.
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
add a comment |
Your Answer
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "3"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398035%2fhow-is-wireshark-constructing-http-flows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
Does this have to do with SEQ and ACK in TCP?
Yes, HTTP/2 and earlier all rely on TCP for keeping track of the packet stream, and TCP uses Seq and Ack numbers for this, along with the 4-tuple of (source IP, source port, destination IP, destination port).
HTTP/2 has additional flow-tracking mechanisms of top of TCP (that HTTP 1.1 and earlier didn't have) because HTTP/2 allows multiple concurrent HTTP transactions within a single TCP stream.
HTTP/3 (the new name for QUIC) is a different story, because it is UDP-based. But I believe it uses a TCP-like Seq/Ack mechanism to keep things straight.
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
add a comment |
Does this have to do with SEQ and ACK in TCP?
Yes, HTTP/2 and earlier all rely on TCP for keeping track of the packet stream, and TCP uses Seq and Ack numbers for this, along with the 4-tuple of (source IP, source port, destination IP, destination port).
HTTP/2 has additional flow-tracking mechanisms of top of TCP (that HTTP 1.1 and earlier didn't have) because HTTP/2 allows multiple concurrent HTTP transactions within a single TCP stream.
HTTP/3 (the new name for QUIC) is a different story, because it is UDP-based. But I believe it uses a TCP-like Seq/Ack mechanism to keep things straight.
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
add a comment |
Does this have to do with SEQ and ACK in TCP?
Yes, HTTP/2 and earlier all rely on TCP for keeping track of the packet stream, and TCP uses Seq and Ack numbers for this, along with the 4-tuple of (source IP, source port, destination IP, destination port).
HTTP/2 has additional flow-tracking mechanisms of top of TCP (that HTTP 1.1 and earlier didn't have) because HTTP/2 allows multiple concurrent HTTP transactions within a single TCP stream.
HTTP/3 (the new name for QUIC) is a different story, because it is UDP-based. But I believe it uses a TCP-like Seq/Ack mechanism to keep things straight.
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
Does this have to do with SEQ and ACK in TCP?
Yes, HTTP/2 and earlier all rely on TCP for keeping track of the packet stream, and TCP uses Seq and Ack numbers for this, along with the 4-tuple of (source IP, source port, destination IP, destination port).
HTTP/2 has additional flow-tracking mechanisms of top of TCP (that HTTP 1.1 and earlier didn't have) because HTTP/2 allows multiple concurrent HTTP transactions within a single TCP stream.
HTTP/3 (the new name for QUIC) is a different story, because it is UDP-based. But I believe it uses a TCP-like Seq/Ack mechanism to keep things straight.
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
answered Jan 24 at 20:03
SpiffSpiff
77.6k10118163
77.6k10118163
add a comment |
add a comment |
Thanks for contributing an answer to Super User!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fsuperuser.com%2fquestions%2f1398035%2fhow-is-wireshark-constructing-http-flows%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
