[
https://issues.apache.org/jira/browse/SLING-422?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Felix Meschberger updated SLING-422:
------------------------------------
Description:
As discussed in [1]: The SlingPostServlet should be default return the correct
HTTP status code and response header(s) instead of 200. The XHTML response
should still be sent. So we come to three cases:
(1) Default: Status code as per the standard with XHTML response containing
further details
(2) "Browser-Friendly": Status code 200 with XHTML response containing actual
status code and further details
(3) Redirect: redirect to another location
Note, that (1) and (2) are almost identical, except for the HTTP status code
being set.
(3) takes place if the :redirect request parameter is set and the processing is
successful. In particular a redirect will not be sent in case an error occurrs
while processing the request even though the :redirect parameter may be set.
(1) or (2) take place in case of a processing error or if the :redirect
parameter is not set. The distinction between (1) and (2) happens according to
the :status parameter. If the parameter is set to "browser" (2) takes place.
Otherwise (1) takes place.
[1] http://markmail.org/message/uf6nwauggkxwrauc
was:
As discussed in [1]: The SlingPostServlet should be default return the correct
HTTP status code and response header(s) instead of 200. The XHTML response
should still be sent. So we come to three cases:
(1) Default: Status code as per the standard with XHTML response containing
further details
(2) "Browser-Friendly": Status code 200 with XHTML response containing actual
status code and further details
(3) Redirect: redirect to another location
Note, that (1) and (2) are almost identical, except for the HTTP status code
being set.
(3) takes place if the :redirect request parameter is set and the processing is
successful. In particular a redirect will not be sent in case an error occurrs
while processing the request even though the :redirect parameter may be set.
(1) or (2) take place in case of a processing error or if the :redirect
parameter is not set. The distinction between (1) and (2) happens according to
the :status parameter. If the parameter is set to "alwayok" (2) takes place.
Otherwise (1) takes place.
[1] http://markmail.org/message/uf6nwauggkxwrauc
Change parameter value to trigger (2) to "browser" as proposed by Bertrand
Delacretaz.
> SlingPostServlet: Return standards complying status code and headers by
> default
> -------------------------------------------------------------------------------
>
> Key: SLING-422
> URL: https://issues.apache.org/jira/browse/SLING-422
> Project: Sling
> Issue Type: Improvement
> Components: Post Servlets
> Reporter: Felix Meschberger
> Assignee: Felix Meschberger
> Fix For: 2.0.0
>
>
> As discussed in [1]: The SlingPostServlet should be default return the
> correct HTTP status code and response header(s) instead of 200. The XHTML
> response should still be sent. So we come to three cases:
> (1) Default: Status code as per the standard with XHTML response containing
> further details
> (2) "Browser-Friendly": Status code 200 with XHTML response containing actual
> status code and further details
> (3) Redirect: redirect to another location
> Note, that (1) and (2) are almost identical, except for the HTTP status code
> being set.
> (3) takes place if the :redirect request parameter is set and the processing
> is successful. In particular a redirect will not be sent in case an error
> occurrs while processing the request even though the :redirect parameter may
> be set.
> (1) or (2) take place in case of a processing error or if the :redirect
> parameter is not set. The distinction between (1) and (2) happens according
> to the :status parameter. If the parameter is set to "browser" (2) takes
> place. Otherwise (1) takes place.
> [1] http://markmail.org/message/uf6nwauggkxwrauc
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
