[
https://issues.apache.org/jira/browse/CAUSEWAY-3976?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andi Huber resolved CAUSEWAY-3976.
----------------------------------
Resolution: Resolved
Caused by the Wicket Viewer failing to properly determine which 'origin' part
of redirect URLs the client sees. The fix is to have client-side JavaScript
that helps with determining the correct URL.
For the fix to work, client-side JavaScript needs to know when it is allowed to
rewrite a redirect URL and when not. This bit of information can be reliably
provided by the server by comparing the URL origin it thinks the client should
see with the origin of the URL the server want the client to redirect to. If
both origins match on the server-side, then the client is allowed to make an
URL rewrite in case it finds an origin mismatch on its side.
> [Wicket Viewer] Table Row Actions Redirect might fail if behind Reverse Proxy
> -----------------------------------------------------------------------------
>
> Key: CAUSEWAY-3976
> URL: https://issues.apache.org/jira/browse/CAUSEWAY-3976
> Project: Causeway
> Issue Type: Bug
> Components: Viewer Wicket
> Reporter: Andi Huber
> Assignee: Andi Huber
> Priority: Major
> Fix For: 4.0.0
>
>
> Resulting page URLs from Table Row Action redirects, may pickup the wrong
> host name.
> Actions called from a different context don't share this issue, so must be a
> bug rather than a configuration issue.
> (backport to v2 is desired)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
