POST method sends data to the server. The type of the body of the request is indicated by the
The difference between
POST is that
PUT is idempotent: calling it once or several times successively has the same effect (that is no side effect), where successive identical
POST may have additional effects, like passing an order several times.
POST request is typically sent via an HTML form and results in a change on the server. In this case, the content type is selected by putting the adequate string in the
enctype attribute of the
<form> element or the
formenctype attribute of the
application/x-www-form-urlencoded: the keys and values are encoded in key-value tuples separated by
'&', with a
'='between the key and the value. Non-alphanumeric characters in both keys and values are percent encoded (en-US): this is the reason why this type is not suitable to use with binary data (use
multipart/form-data: each value is sent as a block of data ("body part"), with a user agent-defined delimiter ("boundary") separating each part. The keys are given in the
Content-Dispositionheader of each part.
POST request is sent via a method other than an HTML form — like via an
XMLHttpRequest — the body can take any type. As described in the HTTP 1.1 specification,
POST is designed to allow a uniform method to cover the following functions:
- Annotation of existing resources
- Posting a message to a bulletin board, newsgroup, mailing list, or similar group of articles;
- Adding a new user through a signup modal;
- Providing a block of data, such as the result of submitting a form, to a data-handling process;
- Extending a database through an append operation.
|Request has body||Yes|
|Successful response has body||Yes|
|Cacheable||Only if freshness information is included|
|Allowed in HTML forms||Yes|
POST /test HTTP/1.1 Host: foo.example Content-Type: application/x-www-form-urlencoded Content-Length: 27 field1=value1&field2=value2
POST /test HTTP/1.1 Host: foo.example Content-Type: multipart/form-data;boundary="boundary" --boundary Content-Disposition: form-data; name="field1" value1 --boundary Content-Disposition: form-data; name="field2"; filename="example.txt" value2 --boundary--
|RFC 7231, section 4.3.3: POST||Hypertext Transfer Protocol (HTTP/1.1): Semantics and Content|
|RFC 2046, section 5.1.1: Common Syntax||Multipurpose Internet Mail Extensions (MIME) Part Two: Media Types|
BCD tables only load in the browser
The compatibility table in this page is generated from structured data. If you'd like to contribute to the data, please check out https://github.com/mdn/browser-compat-data and send us a pull request.