Mixing
Express: Is it necessary to respond with status 200?
Is it necessary to respond with a status 200 code or is the the default behavior?
response.json({
status: 'OK',
});
vs.
response
.status(200)
.json({
status: 'OK',
});
When I hit the route in my browser, I get a 200 response in both cases
By now, I only use status code for other responses than 200 (e.g. 404, 500)
javascript node.js http express server
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
add a comment |
Is it necessary to respond with a status 200 code or is the the default behavior?
response.json({
status: 'OK',
});
vs.
response
.status(200)
.json({
status: 'OK',
});
When I hit the route in my browser, I get a 200 response in both cases
By now, I only use status code for other responses than 200 (e.g. 404, 500)
javascript node.js http express server
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
1
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34
add a comment |
Is it necessary to respond with a status 200 code or is the the default behavior?
response.json({
status: 'OK',
});
vs.
response
.status(200)
.json({
status: 'OK',
});
When I hit the route in my browser, I get a 200 response in both cases
By now, I only use status code for other responses than 200 (e.g. 404, 500)
javascript node.js http express server
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
Is it necessary to respond with a status 200 code or is the the default behavior?
response.json({
status: 'OK',
});
vs.
response
.status(200)
.json({
status: 'OK',
});
When I hit the route in my browser, I get a 200 response in both cases
By now, I only use status code for other responses than 200 (e.g. 404, 500)
javascript node.js http express server
javascript node.js http express server
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
asked Nov 20 '18 at 23:18
marcobiedermannmarcobiedermann
850813
850813
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
1
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34
add a comment |
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
1
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
1
1
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34
add a comment |
1 Answer
1
active
oldest
votes
The Express response object wraps the underlying Node.js response object. In Node.js, if you don't set a response, it will always be 200. Express operates the same way for most requests. It will also automatically handle setting some error response codes for you depending on if and where an error was thrown.
Further, Express will set the response code for you on certain types of routes, for example, if you've defined a redirect, it will automatically set the 302 code for you.
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
add a comment |
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%2f53403078%2fexpress-is-it-necessary-to-respond-with-status-200%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
The Express response object wraps the underlying Node.js response object. In Node.js, if you don't set a response, it will always be 200. Express operates the same way for most requests. It will also automatically handle setting some error response codes for you depending on if and where an error was thrown.
Further, Express will set the response code for you on certain types of routes, for example, if you've defined a redirect, it will automatically set the 302 code for you.
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
add a comment |
The Express response object wraps the underlying Node.js response object. In Node.js, if you don't set a response, it will always be 200. Express operates the same way for most requests. It will also automatically handle setting some error response codes for you depending on if and where an error was thrown.
Further, Express will set the response code for you on certain types of routes, for example, if you've defined a redirect, it will automatically set the 302 code for you.
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
add a comment |
The Express response object wraps the underlying Node.js response object. In Node.js, if you don't set a response, it will always be 200. Express operates the same way for most requests. It will also automatically handle setting some error response codes for you depending on if and where an error was thrown.
Further, Express will set the response code for you on certain types of routes, for example, if you've defined a redirect, it will automatically set the 302 code for you.
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
The Express response object wraps the underlying Node.js response object. In Node.js, if you don't set a response, it will always be 200. Express operates the same way for most requests. It will also automatically handle setting some error response codes for you depending on if and where an error was thrown.
Further, Express will set the response code for you on certain types of routes, for example, if you've defined a redirect, it will automatically set the 302 code for you.
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
answered Nov 20 '18 at 23:31
Matthew HerbstMatthew Herbst
10.7k134687
10.7k134687
add a comment |
add a comment |
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.
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%2f53403078%2fexpress-is-it-necessary-to-respond-with-status-200%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
I wouldn't say it is necessary, but it certainly is the convention.
– Narm
Nov 20 '18 at 23:22
No, it is not necessary. The former does so without calling .status(200). Why ask if you've already confirmed this?
– Kevin B
Nov 20 '18 at 23:26
1
I'd say it's more of a best practice kinda thing... Personally... But no, it's not compulsory by any means.
– JO3-W3B-D3V
Nov 20 '18 at 23:29
@KevinB Thank you for your answer. I was asking because I was not sure about my statement and could not find any answer in the express documentation nor somewhere else. Everyone is using it differently and I was looking for a best practice and even if there might be still some benefit from one over the other
– marcobiedermann
Nov 20 '18 at 23:30
it's not at all a "best practice"... it's just a method you can call if you so choose to. it isn't necessary, you can accept the default, or pass a value to ensure it is what you want it to be.
– Kevin B
Nov 20 '18 at 23:34