This is an automated email from the ASF dual-hosted git repository.

cziegeler pushed a commit to branch master
in repository https://gitbox.apache.org/repos/asf/sling-site.git


The following commit(s) were added to refs/heads/master by this push:
     new 4dcf2a8  SLING-9991 : Parameter :sendError uses/significance should be 
listed in the sling document
4dcf2a8 is described below

commit 4dcf2a8c86a1415915fc46e31f9902247dd88717
Author: Carsten Ziegeler <[email protected]>
AuthorDate: Thu Dec 10 12:36:08 2020 +0100

    SLING-9991 : Parameter :sendError uses/significance should be listed in the 
sling document
---
 .../manipulating-content-the-slingpostservlet-servlets-post.md     | 7 +++++++
 1 file changed, 7 insertions(+)

diff --git 
a/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
 
b/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
index 0e3e9ea..d60e2d3 100644
--- 
a/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
+++ 
b/src/main/jbake/content/documentation/bundles/manipulating-content-the-slingpostservlet-servlets-post.md
@@ -848,6 +848,13 @@ By default the SlingPostServlet sets response status 
according to the status of
 To not send the actual response status back to the client, the `:status` 
request parameter should be set to `browser`. If this parameter is not set, is 
empty, is set to `standard` or to any other value, the actual status code is 
sent back to the client.
 
 
+### `:sendError`
+
+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 `true` the normal error handling using Sling's 
error handlers will be used.
+
+This allows to use custom error handlers for POST requests.
+
+
 ## Response format
 
 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.

Reply via email to