[Reporting] Chromium wait until domcontentloaded not networkidle0 (#23586)
Kibana now keeps a constant connection between the browser and the server from Canvas's websocket. When there's a reverse proxy between the server and the browser, the fallback is XHR polling. This open polling connection was keeping the network alive all the time, never idle, which resulted in the Chromium browser driver kept waiting. Eventually, the Report job would fail with a timeout error.
This commit is contained in:
parent
52723502bc
commit
8d02866321
|
@ -36,7 +36,7 @@ export class HeadlessChromiumDriver {
|
||||||
this.logger.debug(`HeadlessChromiumDriver:opening url ${url}`);
|
this.logger.debug(`HeadlessChromiumDriver:opening url ${url}`);
|
||||||
|
|
||||||
await this.page.setExtraHTTPHeaders(headers);
|
await this.page.setExtraHTTPHeaders(headers);
|
||||||
await this.page.goto(url, { waitUntil: 'networkidle0' });
|
await this.page.goto(url, { waitUntil: 'domcontentloaded' });
|
||||||
await this.page.waitFor(waitForSelector);
|
await this.page.waitFor(waitForSelector);
|
||||||
}
|
}
|
||||||
|
|
||||||
|
|
Loading…
Reference in a new issue