Fixed server-side rendering loading the wrong page

Content captured via server-side rendering could load the wrong thing: specifically, a page pointing at a sub-page or a URL with query parameters. The underlying fetch dropped everything after the base domain, so a URL like example.com/reports/q3?id=42 would load example.com’s home page instead of the report it was supposed to show. It now loads the exact page and parameters you specified.