-
Bug Report
-
Resolution: Fixed
-
L3 - Default
-
None
-
None
-
Not defined
Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/optimize" ), the shared reports show a never ending loading indicator.
Steps to reproduce:
- Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it)
- Create a report and share it
- Open the shared report in an icognito window
Actual result:
The report never loads and keeps showing a never ending loading indicator.
Expected result:
The report should load successfully
Notes:
We could consider also merging this to the 3.9 maintenance branch so that it is part of any future patch
Hints:
Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public.
Testing Notes:
- Set a custom context path in the configuration
- Create a shared report, check that it can be evaluated in an incognito browser
- Create a shared dashboard, check that it can be evaluated in an incognito browser
This is the controller panel for Smart Panels app
[OPT-6704] Shared reports/dashboard does not work if optimize context path is used
| Attachment | New: docker-compose.ccsm.yml [ 57578 ] |
| Description |
Original:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. |
New:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it) * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. |
| Link | New: This issue is related to SUPPORT-15528 [ SUPPORT-15528 ] |
| Status | Original: Triage [ 10612 ] | New: Backlog [ 11212 ] |
| Description |
Original:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it) * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. |
New:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it) * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Notes:* We could consider also merging this to the 3.9 maintenance branch so that it is part of any future patch *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. |
| Assignee | New: Joshua Windels [ joshua.windels ] |
| Status | Original: Backlog [ 11212 ] | New: In Development [ 10312 ] |
| Description |
Original:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it) * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Notes:* We could consider also merging this to the 3.9 maintenance branch so that it is part of any future patch *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. |
New:
h2. Brief summary of the bug. What is it ? Where is it ?
When using an Optimize context path (e.g. running optimize on "http://locahost:8090/{*}optimize{*}" ), the shared reports show a never ending loading indicator. h2. Steps to reproduce: * Use the attached docker file to start optimize (See optimize GitHub home page if you need help running it) * Create a report and share it * Open the shared report in an icognito window h3. Actual result: The report never loads and keeps showing a never ending loading indicator. h3. Expected result: The report should load successfully *Notes:* We could consider also merging this to the 3.9 maintenance branch so that it is part of any future patch *Hints:* Looking at the browser console, it seems that the backend API (the ones with `/api`) requests are getting redirected to an authentication page even though this is a shared and the endpoints are public. *Testing Notes:* * Set a custom context path in the configuration * Create a shared report, check that it can be evaluated in an incognito browser * Create a shared dashboard, check that it can be evaluated in an incognito browser |
| Fix Version/s | New: 3.10.0-alpha5 [ 17995 ] | |
| Fix Version/s | New: 3.9.4 [ 17996 ] |