[
https://issues.apache.org/jira/browse/SLING-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13891937#comment-13891937
]
Bertrand Delacretaz commented on SLING-3374:
--------------------------------------------
There are valid cases for both relative and absolute Location URI in a
response, as described in the draft-ietf-httpbis-p2-semantics-25 that you point
to.
What we might do is override sendRedirect to make sure it respects the
intention (absolute or relative Location) of the caller, using set header + set
status calls as suggested, instead of calling the sendRedirect of the response
object that we wrap.
> Overlay sendRedirect to set relative Location header
> ----------------------------------------------------
>
> Key: SLING-3374
> URL: https://issues.apache.org/jira/browse/SLING-3374
> Project: Sling
> Issue Type: Bug
> Reporter: Laurie byrum
>
> Recently, Location headers returned from redirects started being absolute
> instead of relative.
> We should try to decorate this in sling.
> Can we replace the sendRedirect with a set-header set-status combination
> in sling?
--
This message was sent by Atlassian JIRA
(v6.1.5#6160)
