-
Notifications
You must be signed in to change notification settings - Fork 3.8k
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
[BUG] Request postData() always returns null #9648
Comments
Could you help us reproducing this? |
@pavelfeldman sure. |
The easiest way is to:
|
I forgot to tell you that we have geo location blocking for countries outside EU. This is the reason why video does not start(message is not very helpful in this case). I dont know if you can connect to vpn somewhere in EU. I will double check again about the preflight. |
I can repro this with the following script in Chromium. Works as expected in WebKit, does not load in Firefox. const playwright = require('playwright');
(async () => {
const browser = await playwright.chromium.launch({ headless: false, channel: 'chrome' });
const page = await browser.newPage();
page.on('request', r => {
if (r.url().endsWith('/beat')) {
console.log(r.url(), r.postData(), r.headers());
}
});
await page.goto('https://www.joyn.de/play/trailer/filme/john-wick/john-wick');
})();
In this particular case, |
@dgozman I am glad that you have managed to reproduce it. |
Merging into #6479 |
Just bumped to 1.17 and the issue is still reproducible. Is the fix included in v1.17?
|
It is not fixed yet, the issue was just merged into #6479. |
Thanks I was probably misleaded by the tag v1.17 above. |
Context:
Code Snippet
Listening for request with specific url pattern stopped returning postData.
Describe the bug
Launch browser
Listen for request by specific url pattern
Print request details url, postData, headers
The above test used to work for few months without any issues. I was able to retrive postData and analyze it
The request postData is visible in the browser network tab so its definately not null. It looks like a problem in the communication between browser and playwright library.
.
The text was updated successfully, but these errors were encountered: