-
Type:
Bug
-
Resolution: Unresolved
-
Priority:
Low
-
Component/s: Connect - Frameworks
-
Severity 3 - Minor
-
M
Issue Summary
In a Confluence instance using a custom domain (something different than atlassian.net), the Connect JavaScript AP.navigator.go fails to navigate the user to the requested URL when targeting the original instance URL as an absoluteUrl.
Steps to Reproduce
1. In a Confluence instance with a custom domain, install a Connect app that calls AP.navigator.go(). For this example, let's assume the below URLs for the same instance
| Original URL | Custom URL |
|---|---|
| https://confluence.atlassian.net/wiki | https://custom.confluence.com/wiki |
Where the request will be similar to:
AP.navigator.go("site", {absoluteUrl: "https://confluence.atlassian.net/wiki/pages/viewpage.action?pageId=123456"});
2. Navigate to the iframe responsible for triggering the AP.navigator
Expected Results
The page should open while redirecting to custom.confluence.com/wiki
Actual Results
We get the error in console.
Uncaught Error: Invalid absoluteUrl passed in context
Workaround
If we use a custom domain like this, then AP.navigator will work.
AP.navigator.go("site", {absoluteUrl: "https://custom.confluence.com/wiki/pages/viewpage.action?pageId=123456"});
This might be a good workaround. However, ideally, the original URL should also work, and the browser should then redirect to the custom URL.
- is related to
-
ECOHELP-61481 Loading...