[
https://issues.apache.org/jira/browse/SLING-3374?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14340896#comment-14340896
]
Bertrand Delacretaz commented on SLING-3374:
--------------------------------------------
Good point, Justin!
I checked the SlingHttpServletResponseImpl class of the
org.apache.sling.engine-2.2.0 bundle (used in the CQ 5.4 version that Nitin
refers to) and it's indeed using its parent (servlet engine) class for
sendRedirect, which confirms that the change is due to the servlet engine.
I suggest closing this wontfix as this is a servlet engine issue, with a
workaround (redirect-as-is or something similar) that I don't think we should
implement in Sling.
> 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.3.4#6332)
