You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Solution: user browser frontend passes its window.location.href as extra query parameter to the server (via get_report_pdf(). The server in turn passes the parameters to the headless browser in the renderer. The frontend then uses the passed parameter in Footer.AboutReportColumn.
Also check the PDF export via the API.
The text was updated successfully, but these errors were encountered:
fniessink
changed the title
URL to report in footer of an exported PDF does not contain the FQDN
URL to report in footer of an exported PDF not correct
Nov 3, 2021
For example, if the report URL is http://www.quality-time.example.org/example-report-quality-time, then the URL in the exported PDF will point to http://www/example-report-quality-time. This makes sense as that is the URL that the renderer uses to open the report.
In other environments, we see the correct URL except for the addition of a port, e.g. http://www.quality-time.example.org/example-report-quality-time becomes http://www.quality-time.example.org:2016/example-report-quality-time.
Solution: user browser frontend passes its
window.location.href
as extra query parameter to the server (viaget_report_pdf()
. The server in turn passes the parameters to the headless browser in the renderer. The frontend then uses the passed parameter inFooter.AboutReportColumn
.Also check the PDF export via the API.
The text was updated successfully, but these errors were encountered: