Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

inets: Document sending status with mod_esi #7411

Merged
merged 1 commit into from
Aug 3, 2023
Merged

inets: Document sending status with mod_esi #7411

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
9 changes: 8 additions & 1 deletion lib/inets/doc/src/mod_esi.xml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -150,7 +150,14 @@
that is, <c>"\r\n\r\n",</c> the server assumes that no HTTP
header fields will be generated.</p>

<p><c>Env</c> environment data of the request see description above.</p>
<p>To set the response status code, the special <c>status</c> response
header can be sent. For instance, to acknowledge creation of a resource
and annotate the response content type with JSON, one could respond with
the following headers:</p>

<code type="erl">"status: 201 Created\r\n content-type: application/json\r\n\r\n"</code>

<p><c>Env</c> environment data of the request, see description above.</p>

<p><c>Input</c> is query data of a GET request or the body of
a PUT or POST request. The default behavior (legacy reasons)
Expand Down