Why aren't network requests for iFrames showing in the Chrome developer tools under Selenium?
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 asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
add a comment |
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 asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
add a comment |
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 asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
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 '18 at 12:05
AndrewAndrew
3271315
asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
asked Nov 13 '18 at 12:05
AndrewAndrew
3271315
3271315
add a comment |
add a comment |
1 Answer
1
active
oldest
votes
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 '18 at 17:00
AndrewAndrew
3271315
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
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
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
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 '18 at 17:00
AndrewAndrew
3271315
add a comment |
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 '18 at 17:00
AndrewAndrew
3271315
add a comment |
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 '18 at 17:00
AndrewAndrew
3271315
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 '18 at 17:00
AndrewAndrew
3271315
answered Nov 22 '18 at 17:00
AndrewAndrew
3271315
answered Nov 22 '18 at 17:00
AndrewAndrew
3271315
answered Nov 22 '18 at 17:00
AndrewAndrew
3271315
3271315
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
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
