This is an automated email from the ASF dual-hosted git repository.
git-site-role pushed a commit to branch asf-site
in repository https://gitbox.apache.org/repos/asf/sling-site.git
The following commit(s) were added to refs/heads/asf-site by this push:
new 74cbfb6 Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/88/
74cbfb6 is described below
commit 74cbfb624d07f2901cc49f1416b40ab7f4cb0b77
Author: jenkins <[email protected]>
AuthorDate: Thu Dec 10 11:41:58 2020 +0000
Automatic website deployment from
https://ci-builds.apache.org/job/Sling/job/modules/job/sling-site/job/master/88/
---
.../manipulating-content-the-slingpostservlet-servlets-post.html | 5 ++++-
1 file changed, 4 insertions(+), 1 deletion(-)
diff --git
a/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
b/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
index e554af2..b46f0b6 100644
---
a/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
+++
b/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.html
@@ -718,6 +718,9 @@ See <a
href="https://issues.apache.org/jira/browse/SLING-8186";>SLING-8186</a> an
<h3><a href="#status" id="status"><code>:status</code></a></h3>
<p>By default the SlingPostServlet sets response status according to the
status of the operation executed. In some cases, it may be desirable to not
have the real status codes (e.g. 404 or 505) but a normal <em>200/OK</em> to
trick the client browser into displaying the response content generated by the
SlingPostServlet.</p>
<p>To not send the actual response status back to the client, the
<code>:status</code> request parameter should be set to <code>browser</code>.
If this parameter is not set, is empty, is set to <code>standard</code> or to
any other value, the actual status code is sent back to the client.</p>
+<h3><a href="#senderror" id="senderror"><code>:sendError</code></a></h3>
+<p>By default the SlingPostServlet generates an error response based on a
template and does not use the normal Sling error handling. If this parameter is
specified with the value of <code>true</code> the normal error handling using
Sling's error handlers will be used.</p>
+<p>This allows to use custom error handlers for POST requests.</p>
<h2><a href="#response-format" id="response-format">Response format</a></h2>
<p>The SlingPostServlet produces a basic HTTP response body, listing the
response status, what changes have been made, and other meta-data about the
result of the POST request.</p>
<p>The format of this response is either HTML or JSON (JSON support introduced
with <a
href="https://issues.apache.org/jira/browse/SLING-1336";>SLING-1336</a>).
SlingPostServlet determines which format to use by examining the Accept header
of the incoming request. If the client has specified a preference for the media
type "application/json", the JSON format is used, otherwise HTML is
returned. The Accept header can be overridden (and simulated) by posting a
:http-equiv-accept f [...]
@@ -761,7 +764,7 @@ See <a
href="https://issues.apache.org/jira/browse/SLING-8186";>SLING-8186</a> an
</div><footer class="footer">
<div class="content has-text-centered is-small">
<div class="revisionInfo">
- Last modified by <span class="author">Bertrand
Delacretaz</span> on <span class="comment">Mon Mar 23 17:39:14 2020 +0100</span>
+ Last modified by <span class="author">Carsten
Ziegeler</span> on <span class="comment">Thu Dec 10 12:36:08 2020 +0100</span>
</div> <p>
Apache Sling, Sling, Apache, the Apache feather logo,
and the Apache Sling project logo are trademarks of The Apache Software
Foundation. All other marks mentioned may be trademarks or registered
trademarks of their respective owners.
</p><p>
