Overview[1]#
HTTP POST is a HTTP Method which requests that the server accept the entity enclosed in the request as a new subordinate of the web resource identified by the URI.The data POSTed might be, for example, an annotation for existing resources; a message for a bulletin board, newsgroup, mailing list, or comment thread; a block of data that is the result of submitting a web form to a data-handling process; or an item to add to a database.
HTTP POST do NOT Cache]#
An interesting point on HTTP POST vs HTTP GET is that HTTP POST do NOT Cache] which can be an issue for some API calls.More Information#
There might be more information for this subject on one of the following:- Accept header
- Authentication Request
- Authorization_endpoint
- Best Practices OpenID Connect
- Client Authentication Methods
- Client_secret_post
- Content-Type
- Create Read Update Delete
- Form Post Response Mode
- Form Serialization
- HTTP 200
- HTTP 301
- HTTP 302
- HTTP Method
- HTTP Status Code
- Initiate_login_uri
- Logging Out
- Micropub
- OAuth 2.0 Vulnerabilities
- OAuth Token Request
- Registration_endpoint
- Representational State Transfer
- Resource Action
- Resource Owner Password Credentials Grant
- Revocation_endpoint
- SAML Bindings
- SCIM Bulk Request
- SCIM Create Request
- SCIM Resource Operations
- Session
- Socket Secure
- Userinfo_endpoint
- Web Blog_blogentry_180216_1
- What is missing in OAuth 2.0
- [#1] - Request methods
- based on information obtained 2016-05-21-
