-
Notifications
You must be signed in to change notification settings - Fork 9.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Page loading stucks on header manipulation if page give 302 status code #3973
Comments
Minimum reproducible case: if 'use strict';
const puppeteer = require('puppeteer');
(async () => {
try {
let browser = await puppeteer.launch({ headless: false });
let [page] = await browser.pages();
await page.setRequestInterception(true);
page.on('request', request => {
const headers = Object.assign({}, request.headers(), {
// foo: 'bar'
});
request.continue({ headers });
});
await page.goto('https://is.gd/OwycZW');
} catch (err) {
console.error(err);
}
})(); |
this is a really annoying bug, did somebody find any workaround or solution for it? |
hi @aslushnikov |
This is a chromium bug; filed upstream as https://crbug.com/937719 Thanks for reporting this! |
I get the same result when I send POST data and the page give 302 status code. |
We're marking this issue as unconfirmed because it has not had recent activity and we weren't able to confirm it yet. It will be closed if no further activity occurs within the next 30 days. |
We are closing this issue. If the issue still persists in the latest version of Puppeteer, please reopen the issue and update the description. We will try our best to accomodate it! |
Steps to reproduce
Tell us about your environment:
--
What steps will reproduce the problem?
below code can reproduce this error.
What is the expected result?
header should be manipulated and redirected to other page if page response status code is 302
What happens instead?
page loading forever in pending status
The text was updated successfully, but these errors were encountered: