when I must use PUT (or another method) request over POST?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty{ height:90px;width:728px;box-sizing:border-box;
}
apart from GET method,
we can make POST implement the request typically as any other http method, so why we should use other methods rather than POST?
POST='delete some data from this resource'
also we can make the POST idempotence by ignoring the subsequent requests (ignoring that PUT can create a new resource)
http post http-headers http-post put
asked Nov 25 '18 at 8:53
xx yyxx yy
598
add a comment |
apart from GET method,
we can make POST implement the request typically as any other http method, so why we should use other methods rather than POST?
POST='delete some data from this resource'
also we can make the POST idempotence by ignoring the subsequent requests (ignoring that PUT can create a new resource)
http post http-headers http-post put
asked Nov 25 '18 at 8:53
xx yyxx yy
598
add a comment |
apart from GET method,
we can make POST implement the request typically as any other http method, so why we should use other methods rather than POST?
POST='delete some data from this resource'
also we can make the POST idempotence by ignoring the subsequent requests (ignoring that PUT can create a new resource)
http post http-headers http-post put
asked Nov 25 '18 at 8:53
xx yyxx yy
598
apart from GET method,
we can make POST implement the request typically as any other http method, so why we should use other methods rather than POST?
POST='delete some data from this resource'
also we can make the POST idempotence by ignoring the subsequent requests (ignoring that PUT can create a new resource)
http post http-headers http-post put
http post http-headers http-post put
asked Nov 25 '18 at 8:53
xx yyxx yy
598
asked Nov 25 '18 at 8:53
xx yyxx yy
598
asked Nov 25 '18 at 8:53
xx yyxx yy
598
asked Nov 25 '18 at 8:53
xx yyxx yy
598
asked Nov 25 '18 at 8:53
xx yyxx yy
598
598
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
Well, actually you could also use only GET and DELETE requests for everything. It's only the question how the backend handles these specific request types.
If you want to follow the rules, then you would usually develop so that you provide conformity to usual standards (PUT for creation, DELETE for deletion) and so on.
Can somehow be compared to response status codes. Of course I could return the response code 200 and 201 for "Unauthorized", as response codes can be defined individually. But that's against every standard and should not be done.
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
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%2f53465984%2fwhen-i-must-use-put-or-another-method-request-over-post%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
Well, actually you could also use only GET and DELETE requests for everything. It's only the question how the backend handles these specific request types.
If you want to follow the rules, then you would usually develop so that you provide conformity to usual standards (PUT for creation, DELETE for deletion) and so on.
Can somehow be compared to response status codes. Of course I could return the response code 200 and 201 for "Unauthorized", as response codes can be defined individually. But that's against every standard and should not be done.
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
add a comment |
Well, actually you could also use only GET and DELETE requests for everything. It's only the question how the backend handles these specific request types.
If you want to follow the rules, then you would usually develop so that you provide conformity to usual standards (PUT for creation, DELETE for deletion) and so on.
Can somehow be compared to response status codes. Of course I could return the response code 200 and 201 for "Unauthorized", as response codes can be defined individually. But that's against every standard and should not be done.
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
add a comment |
Well, actually you could also use only GET and DELETE requests for everything. It's only the question how the backend handles these specific request types.
If you want to follow the rules, then you would usually develop so that you provide conformity to usual standards (PUT for creation, DELETE for deletion) and so on.
Can somehow be compared to response status codes. Of course I could return the response code 200 and 201 for "Unauthorized", as response codes can be defined individually. But that's against every standard and should not be done.
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
Well, actually you could also use only GET and DELETE requests for everything. It's only the question how the backend handles these specific request types.
If you want to follow the rules, then you would usually develop so that you provide conformity to usual standards (PUT for creation, DELETE for deletion) and so on.
Can somehow be compared to response status codes. Of course I could return the response code 200 and 201 for "Unauthorized", as response codes can be defined individually. But that's against every standard and should not be done.
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
answered Nov 25 '18 at 9:00
GutelaunetypGutelaunetyp
18010
18010
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
add a comment |
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
@xxyy no problem. Please don't forget to mark this answer as accepted, if your question has been answered. Appreciate that.
– Gutelaunetyp
Nov 25 '18 at 9:04
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%2f53465984%2fwhen-i-must-use-put-or-another-method-request-over-post%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
