HTTP响应的头和正文之间是有区别的。PUT永远不应该返回正文，但必须在报头中返回响应代码。如果成功就选择200，如果不成功就选择4xx。没有空返回码这样的东西。你为什么想做这个?

HTTP/1.1规范(第9.6节)讨论了适当的响应/错误代码。但是，它不处理响应内容。

你想要什么?一个简单的HTTP响应代码(200等)对我来说似乎是直接而明确的。

“Created”的Http响应代码201以及指向客户端可以找到新创建资源的“Location”标头。

看起来好…虽然我认为一个基本的指示成功/失败/时间张贴/#字节接收/等等。会更好。

编辑:我一直在考虑数据完整性和/或记录保存;元数据，如MD5散列或接收时间的时间戳，可能对大型数据文件有帮助。

HTTP响应的头和正文之间是有区别的。PUT永远不应该返回正文，但必须在报头中返回响应代码。如果成功就选择200，如果不成功就选择4xx。没有空返回码这样的东西。你为什么想做这个?

HTTP规范(RFC 2616)有许多适用的建议。以下是我的解读:

HTTP status code 200 OK for a successful PUT of an update to an existing resource. No response body needed. (Per Section 9.6, 204 No Content is even more appropriate.) HTTP status code 201 Created for a successful PUT of a new resource, with the most specific URI for the new resource returned in the Location header field and any other relevant URIs and metadata of the resource echoed in the response body. (RFC 2616 Section 10.2.2) HTTP status code 409 Conflict for a PUT that is unsuccessful due to a 3rd-party modification, with a list of differences between the attempted update and the current resource in the response body. (RFC 2616 Section 10.4.10) HTTP status code 400 Bad Request for an unsuccessful PUT, with natural-language text (such as English) in the response body that explains why the PUT failed. (RFC 2616 Section 10.4)