Why aren't network requests for iFrames showing in the Chrome developer tools under Selenium?
up vote
0
down vote
favorite
I have a use case where I need to retrieve the initiator from the Chrome Network tab. This works fine, except for the following case:
- The iframe is HTTPS;
- The enclosing page is HTTP;
- The page was opened by Selenium
In this case, the network tab (and any extension on the debug protocol) show the fetch to the iframe content remains pending forever, and none of the child loads are emitted.
Changing the page URL to HTTPS, then the iframe is loaded and the child loads are displayed.
If I manually control the Selenium-opened browser and open a new tab, then it does not matter if the fetch is over HTTP or HTTPS. It really is only the tab that webdriver creates when it's loaded that seems to suffer this effect.
Is there some security protection at play, or is this just a weird bug?
webdriver google-chrome-devtools selenium-chromedriver google-contacts
add a comment |
up vote
0
down vote
favorite
I have a use case where I need to retrieve the initiator from the Chrome Network tab. This works fine, except for the following case:
- The iframe is HTTPS;
- The enclosing page is HTTP;
- The page was opened by Selenium
In this case, the network tab (and any extension on the debug protocol) show the fetch to the iframe content remains pending forever, and none of the child loads are emitted.
Changing the page URL to HTTPS, then the iframe is loaded and the child loads are displayed.
If I manually control the Selenium-opened browser and open a new tab, then it does not matter if the fetch is over HTTP or HTTPS. It really is only the tab that webdriver creates when it's loaded that seems to suffer this effect.
Is there some security protection at play, or is this just a weird bug?
webdriver google-chrome-devtools selenium-chromedriver google-contacts
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I have a use case where I need to retrieve the initiator from the Chrome Network tab. This works fine, except for the following case:
- The iframe is HTTPS;
- The enclosing page is HTTP;
- The page was opened by Selenium
In this case, the network tab (and any extension on the debug protocol) show the fetch to the iframe content remains pending forever, and none of the child loads are emitted.
Changing the page URL to HTTPS, then the iframe is loaded and the child loads are displayed.
If I manually control the Selenium-opened browser and open a new tab, then it does not matter if the fetch is over HTTP or HTTPS. It really is only the tab that webdriver creates when it's loaded that seems to suffer this effect.
Is there some security protection at play, or is this just a weird bug?
webdriver google-chrome-devtools selenium-chromedriver google-contacts
I have a use case where I need to retrieve the initiator from the Chrome Network tab. This works fine, except for the following case:
- The iframe is HTTPS;
- The enclosing page is HTTP;
- The page was opened by Selenium
In this case, the network tab (and any extension on the debug protocol) show the fetch to the iframe content remains pending forever, and none of the child loads are emitted.
Changing the page URL to HTTPS, then the iframe is loaded and the child loads are displayed.
If I manually control the Selenium-opened browser and open a new tab, then it does not matter if the fetch is over HTTP or HTTPS. It really is only the tab that webdriver creates when it's loaded that seems to suffer this effect.
Is there some security protection at play, or is this just a weird bug?
webdriver google-chrome-devtools selenium-chromedriver google-contacts
webdriver google-chrome-devtools selenium-chromedriver google-contacts
asked Nov 13 at 12:05
Andrew
3221315
3221315
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
up vote
0
down vote
This appears to be caused by Out-of-Process iFrame Isolation.
By passing --disable-features=IsolateOrigins,site-per-process
to the Chrome process, then the iFrame network traces show up.
add a comment |
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
up vote
0
down vote
This appears to be caused by Out-of-Process iFrame Isolation.
By passing --disable-features=IsolateOrigins,site-per-process
to the Chrome process, then the iFrame network traces show up.
add a comment |
up vote
0
down vote
This appears to be caused by Out-of-Process iFrame Isolation.
By passing --disable-features=IsolateOrigins,site-per-process
to the Chrome process, then the iFrame network traces show up.
add a comment |
up vote
0
down vote
up vote
0
down vote
This appears to be caused by Out-of-Process iFrame Isolation.
By passing --disable-features=IsolateOrigins,site-per-process
to the Chrome process, then the iFrame network traces show up.
This appears to be caused by Out-of-Process iFrame Isolation.
By passing --disable-features=IsolateOrigins,site-per-process
to the Chrome process, then the iFrame network traces show up.
answered Nov 22 at 17:00
Andrew
3221315
3221315
add a comment |
add a comment |
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53280678%2fwhy-arent-network-requests-for-iframes-showing-in-the-chrome-developer-tools-un%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown