Skip to content

Commit

Permalink
README: Clarifying Content-Type in SMTP body endpoints
Browse files Browse the repository at this point in the history
  • Loading branch information
Lucas Hinderberger committed Jun 25, 2024
1 parent 0ca8817 commit 7634e45
Showing 1 changed file with 6 additions and 0 deletions.
6 changes: 6 additions & 0 deletions README.md
Original file line number Diff line number Diff line change
Expand Up @@ -2711,6 +2711,9 @@ for the message with the corresponding index.
If the message was sent with a `Content-Transfer-Encoding` of either `base64`
or `quoted-printable`, the endpoint returns the decoded body.

If the message was sent with a `Content-Type` header, it will be passed through
to the HTTP response.

#### /smtp/$idx/multipart
For multipart messages, the `/smtp/$idx/multipart` endpoint (e.g.
`/smtp/1/multipart`) will contain an index of that messages multiparts in the
Expand Down Expand Up @@ -2767,3 +2770,6 @@ is made available.

If the multipart was sent with a `Content-Transfer-Encoding` of either `base64`
or `quoted-printable`, the endpoint returns the decoded body.

If the message was sent with a `Content-Type` header, it will be passed through
to the HTTP response.

0 comments on commit 7634e45

Please sign in to comment.