HTTP/1.1 body length calculate
The web server does not close the connection after sending a 401 Unauthorized like this:
HTTP/1.1 401 Unauthorizedrn
Date: Fri, 23 Nov 2018 10:50:52 GMTrn
Server: DNVRS-Websrn
Cache-Control: no-cachern
Content-Type: text/htmlrn
Connection: closern
WWW-Authenticate: Digest realm="DVRNVRDVS", domain="::", qop="auth", nonce="e7db4eb94dd16ef9f0ff8c56d349ca94:1542970252377", opaque="", algorithm="MD5", stale="FALSE"rn
WWW-Authenticate: Basic realm="DVRNVRDVS"rn
rn
rn
According to RFC7230 3.3.3 Message Body Length
- Otherwise, this is a response message without a declared message
body length, so the message body length is determined by the
number of octets received prior to the server closing the
connection.
Is this behavior valid?
Edit:
What's more, another web server doesn't have the last rn line, does that matter?
Edit: According to 6.6 Tear-down part:
A server that sends a "close" connection option MUST initiate a close
of the connection (see below) after it sends the response containing
"close". The server MUST NOT process any further requests received
on that connection.
What does this initiate a close of the connection mean?
Does this
To avoid the TCP reset problem, servers typically close a connection
in stages
means that the web server needn't close the connection immediately?
http
asked Nov 23 '18 at 3:05
Morris
15529
add a comment |
The web server does not close the connection after sending a 401 Unauthorized like this:
HTTP/1.1 401 Unauthorizedrn
Date: Fri, 23 Nov 2018 10:50:52 GMTrn
Server: DNVRS-Websrn
Cache-Control: no-cachern
Content-Type: text/htmlrn
Connection: closern
WWW-Authenticate: Digest realm="DVRNVRDVS", domain="::", qop="auth", nonce="e7db4eb94dd16ef9f0ff8c56d349ca94:1542970252377", opaque="", algorithm="MD5", stale="FALSE"rn
WWW-Authenticate: Basic realm="DVRNVRDVS"rn
rn
rn
According to RFC7230 3.3.3 Message Body Length
- Otherwise, this is a response message without a declared message
body length, so the message body length is determined by the
number of octets received prior to the server closing the
connection.
Is this behavior valid?
Edit:
What's more, another web server doesn't have the last rn line, does that matter?
Edit: According to 6.6 Tear-down part:
A server that sends a "close" connection option MUST initiate a close
of the connection (see below) after it sends the response containing
"close". The server MUST NOT process any further requests received
on that connection.
What does this initiate a close of the connection mean?
Does this
To avoid the TCP reset problem, servers typically close a connection
in stages
means that the web server needn't close the connection immediately?
http
asked Nov 23 '18 at 3:05
Morris
15529
add a comment |
The web server does not close the connection after sending a 401 Unauthorized like this:
HTTP/1.1 401 Unauthorizedrn
Date: Fri, 23 Nov 2018 10:50:52 GMTrn
Server: DNVRS-Websrn
Cache-Control: no-cachern
Content-Type: text/htmlrn
Connection: closern
WWW-Authenticate: Digest realm="DVRNVRDVS", domain="::", qop="auth", nonce="e7db4eb94dd16ef9f0ff8c56d349ca94:1542970252377", opaque="", algorithm="MD5", stale="FALSE"rn
WWW-Authenticate: Basic realm="DVRNVRDVS"rn
rn
rn
According to RFC7230 3.3.3 Message Body Length
- Otherwise, this is a response message without a declared message
body length, so the message body length is determined by the
number of octets received prior to the server closing the
connection.
Is this behavior valid?
Edit:
What's more, another web server doesn't have the last rn line, does that matter?
Edit: According to 6.6 Tear-down part:
A server that sends a "close" connection option MUST initiate a close
of the connection (see below) after it sends the response containing
"close". The server MUST NOT process any further requests received
on that connection.
What does this initiate a close of the connection mean?
Does this
To avoid the TCP reset problem, servers typically close a connection
in stages
means that the web server needn't close the connection immediately?
http
asked Nov 23 '18 at 3:05
Morris
15529
The web server does not close the connection after sending a 401 Unauthorized like this:
HTTP/1.1 401 Unauthorizedrn
Date: Fri, 23 Nov 2018 10:50:52 GMTrn
Server: DNVRS-Websrn
Cache-Control: no-cachern
Content-Type: text/htmlrn
Connection: closern
WWW-Authenticate: Digest realm="DVRNVRDVS", domain="::", qop="auth", nonce="e7db4eb94dd16ef9f0ff8c56d349ca94:1542970252377", opaque="", algorithm="MD5", stale="FALSE"rn
WWW-Authenticate: Basic realm="DVRNVRDVS"rn
rn
rn
According to RFC7230 3.3.3 Message Body Length
- Otherwise, this is a response message without a declared message
body length, so the message body length is determined by the
number of octets received prior to the server closing the
connection.
Is this behavior valid?
Edit:
What's more, another web server doesn't have the last rn line, does that matter?
Edit: According to 6.6 Tear-down part:
A server that sends a "close" connection option MUST initiate a close
of the connection (see below) after it sends the response containing
"close". The server MUST NOT process any further requests received
on that connection.
What does this initiate a close of the connection mean?
Does this
To avoid the TCP reset problem, servers typically close a connection
in stages
means that the web server needn't close the connection immediately?
http
http
asked Nov 23 '18 at 3:05
Morris
15529
asked Nov 23 '18 at 3:05
Morris
15529
edited Nov 23 '18 at 10:11
asked Nov 23 '18 at 3:05
Morris
15529
asked Nov 23 '18 at 3:05
Morris
15529
asked Nov 23 '18 at 3:05
Morris
15529
15529
add a comment |
add a comment |
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
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%2fstackoverflow.com%2fquestions%2f53440184%2fhttp-1-1-body-length-calculate%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
Thanks for contributing an answer to Stack Overflow!
- 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.
Some of your past answers have not been well-received, and you're in danger of being blocked from answering.
Please pay close attention to the following guidance:
- 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%2fstackoverflow.com%2fquestions%2f53440184%2fhttp-1-1-body-length-calculate%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
