The HTTP PUT
request method creates a new resource or replaces a representation of the target resource with the request payload.
The difference between PUT
and POST
is that PUT
is idempotent: calling it once or several times successively has the same effect (that is no side effect), whereas successive identical POST
requests may have additional effects, akin to placing an order several times.
Request has body | Yes |
---|---|
Successful response has body | No |
Safe | No |
Idempotent | Yes |
Cacheable | No |
Allowed in HTML forms | No |
Syntax
PUT /new.html HTTP/1.1
Example
Request
PUT /new.html HTTP/1.1 Host: example.com Content-type: text/html Content-length: 16 <p>New File</p>
Responses
If the target resource does not have a current representation and the PUT
request successfully creates one, then the origin server must inform the user agent by sending a 201
(Created
) response.
HTTP/1.1 201 Created Content-Location: /new.html
If the target resource does have a current representation and that representation is successfully modified in accordance with the state of the enclosed representation, then the origin server must send either a 200
(OK
) or a 204
(No Content
) response to indicate successful completion of the request.
HTTP/1.1 204 No Content Content-Location: /existing.html
Specifications
Specification | Title |
---|---|
RFC 7231, section 4.3.4: PUT | Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content |
Browser compatibility
Desktop | Mobile | |||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
PUT | Chrome Full support Yes | Edge Full support 12 | Firefox Full support Yes | IE Full support Yes | Opera Full support Yes | Safari Full support Yes | WebView Android Full support Yes | Chrome Android Full support Yes | Firefox Android Full support Yes | Opera Android Full support Yes | Safari iOS Full support Yes | Samsung Internet Android Full support Yes |
Legend
- Full support
- Full support