[
https://issues.apache.org/jira/browse/SLING-3373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Laurie byrum updated SLING-3373:
--------------------------------
Description:
We’re now returning the absolute path in the Location header instead of a
relative path. For example:
http://localhost:4503/content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
vs
/content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
It was suggested that we should try to patch this in jetty or decorate it in
sling.
Can we replace the sendRedirect with a set-header set-status combination in
sling?
was:
We’re now returning the absolute path in the Location header instead of a
relative path. For example:
http://localhost:4503/content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
vs
/content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
This looks like a consequence of our switch from CQSE to Jetty. It was
suggested that we should try to patch this in jetty or decorate it in sling.
Can we replace the sendRedirect with a set-header set-status combination in
sling?
> Location header from sling redirects is now absolute
> ----------------------------------------------------
>
> Key: SLING-3373
> URL: https://issues.apache.org/jira/browse/SLING-3373
> Project: Sling
> Issue Type: Bug
> Components: General
> Reporter: Laurie byrum
>
> We’re now returning the absolute path in the Location header instead of a
> relative path. For example:
> http://localhost:4503/content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
> vs
> /content/usergenerated/content/geometrixx-outdoors/en/mypage/blah/blah
>
> It was suggested that we should try to patch this in jetty or decorate it 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)
