PUT vs POST in REST
2016-07-07 14:38
357 查看
来自:http://stackoverflow.com/questions/630453/put-vs-post-in-rest
http://www.15yan.com/story/7dz6oXiSHeq/
Overall:
Both PUT and POST can be used for creating.
You have to ask "what are you performing the action to?" to distinguish what you should be using. Let's assume you're designing an API for asking questions. If you want to use POST then you would do that to a list of questions. If you want to use PUT then you would do that to a particular question.
Great both can be used, so which one should I use in my RESTful design:
You do not need to support both PUT and POST.
Which is used is left up to you. But just remember to use the right one depending on what object you are referencing in the request.
Some considerations:
Do you name your URL objects you create explicitly, or let the server decide? If you name them then use PUT. If you let the server decide then use POST.
PUT is idempotent, so if you PUT an object twice, it has no effect. This is a nice property, so I would use PUT when possible.
You can update or create a resource with PUT with the same object URL
With POST you can have 2 requests coming in at the same time making modifications to a URL, and they may update different parts of the object.
An example:
I wrote the following as part of another answer on SO regarding this:
POST:
Used to modify and update a resource
Note that the following is an error:
If the URL is not yet created, you should not be using POST to create it while specifying the name. This should result in a 'resource not found' error because
You could though do something like this to create a resources using POST:
Note that in this case the resource name is not specified, the new objects URL path would be returned to you.
PUT:
Used to create a resource, or overwrite it. While you specify the resources new URL.
For a new resource:
To overwrite an existing resource:
http://www.15yan.com/story/7dz6oXiSHeq/
Overall:
Both PUT and POST can be used for creating.
You have to ask "what are you performing the action to?" to distinguish what you should be using. Let's assume you're designing an API for asking questions. If you want to use POST then you would do that to a list of questions. If you want to use PUT then you would do that to a particular question.
Great both can be used, so which one should I use in my RESTful design:
You do not need to support both PUT and POST.
Which is used is left up to you. But just remember to use the right one depending on what object you are referencing in the request.
Some considerations:
Do you name your URL objects you create explicitly, or let the server decide? If you name them then use PUT. If you let the server decide then use POST.
PUT is idempotent, so if you PUT an object twice, it has no effect. This is a nice property, so I would use PUT when possible.
You can update or create a resource with PUT with the same object URL
With POST you can have 2 requests coming in at the same time making modifications to a URL, and they may update different parts of the object.
An example:
I wrote the following as part of another answer on SO regarding this:
POST:
Used to modify and update a resource
POST /questions/<existing_question> HTTP/1.1 Host: www.example.com/
Note that the following is an error:
POST /questions/<new_question> HTTP/1.1 Host: www.example.com/
If the URL is not yet created, you should not be using POST to create it while specifying the name. This should result in a 'resource not found' error because
<new_question>does not exist yet. You should PUT the
<new_question>resource on the server first.
You could though do something like this to create a resources using POST:
POST /questions HTTP/1.1 Host: www.example.com/
Note that in this case the resource name is not specified, the new objects URL path would be returned to you.
PUT:
Used to create a resource, or overwrite it. While you specify the resources new URL.
For a new resource:
PUT /questions/<new_question> HTTP/1.1 Host: www.example.com/
To overwrite an existing resource:
PUT /questions/<existing_question> HTTP/1.1 Host: www.example.com/
相关文章推荐
- HTML5应用程序缓存Application Cache
- LeetCode 17 Letter Combinations of a Phone Number
- 无用的知识
- iOS开发-常用第三方开源框架介绍
- Linux基础知识之帮助命令的使用
- 利用MyBatis Generator自动创建代码
- svn--使用MyEclipse插件
- 在CentOS上安装nginx服务器
- Uva 540 - Team Queue
- NTFS数据流及高级文件隐藏
- HTTP.sys漏洞验证及防护
- 转 手把手教你最简单的开源项目托管GitHub入门教程
- 欢迎使用CSDN-markdown编辑器
- iOS-最全的App上架教程
- Java基础知识--补充
- 给 Android 开发者的 RxJava 详解
- Android利用canvas画各种图形(点、直线、弧、圆、椭圆、文字、矩形、多边形、曲线、圆角矩形)
- 给 Android 开发者的 RxJava 详解
- 给 Android 开发者的 RxJava 详解
- 给 Android 开发者的 RxJava 详解