/ HTTP Headers


The Accept-Post HTTP response header, a component of the HTTP/1.1 protocol, is critical for communicating server-side media type constraints for POST requests. This header indicates the media types that a server can process, typically presented as MIME types. This article will delve into the specifics of the Accept-Post header, its usage, and some practical scenarios.

Exploring the Accept-Post Header

The Accept-Post header finds its place exclusively in HTTP response messages and doesn’t feature in requests. As an informative header, it is not required to be present in all HTTP responses. However, it becomes relevant when dealing with resources that support the POST method, aiding in constraining the client-side request format.

A typical representation of this header might look like this:

Accept-Post: text/plain, application/json

In this instance, text/plain and application/json are the media types that the server is prepared to accept for processing in POST requests.

HTTP Request and Response Featuring Accept-Post

Let’s observe an HTTP exchange scenario to understand the Accept-Post header’s role better.

Suppose a client sends a GET request to the server:

GET /resource/123 HTTP/1.1
Host: www.example.com

The server can respond with resource details and include the Accept-Post header to indicate the formats it can accept for POST requests:

HTTP/1.1 200 OK
Content-Type: application/json
Accept-Post: application/json

  "id": "123",
  "name": "John Doe",
  "email": "john@example.com"

The Accept-Post header value in this response signifies that the server accepts JSON format for processing POST requests.

If the client decides to submit data to the resource using a POST request, it should format the request body according to the Accept-Post values:

POST /resource HTTP/1.1
Host: www.example.com
Content-Type: application/json

  "name": "Jane Doe",
  "email": "jane@example.com"

Here, the client is sending data in a JSON format that the server is equipped to process, as indicated by the Accept-Post header in the previous response.

Considerations in Usage

Remember, while the Accept-Post header is useful for communicating acceptable media types, its presence is not mandatory. It becomes significant when dealing with resources that can process POST requests. As a best practice, a client should inspect the Accept-Post header’s values before dispatching a POST request to ensure the data is sent in an acceptable format.


In essence, the Accept-Post HTTP header plays a significant role in informing clients about the media types a server can handle for POST requests. Although it’s not universally required, it’s particularly beneficial when dealing with resources that allow POST operations. As a developer, understanding and implementing this HTTP header properly can optimize client-server communication, leading to more efficient data transmission and fewer unsupported media type errors. By mastering this header, you’re one step closer to designing robust, interoperable web services.

Was this helpful?

Thanks for your feedback!