There's been a few changes here: (1) https-first (which had fixed this in Nightly) no longer helps here anymore, as of bug 1919544 (2) ...but this also fails in Chrome nowadays, if I perform the exact same steps and start in the same fresh-user-profile state. I don't know for sure if that's a change in Chrome's behavior or a change in the site or a change in testing methodology. To actually test here, it's important to start with a fresh user-profile, because the HTTPS version of the NIH website sends a HSTS header which forces the browser to auto-upgrade any future http URLs to be https. So as soon as you actually visit the https site, then you'll get expected-results from that point onwards (regardless of browser). So that's why you have to start with a fresh user-profile here. In Chrome, the easiest way to do that is to click the "user-profile menu" just to the left of their 3-dot-menu button, and then choose "Open Guest Profile". Comparing Firefox (135 Nightly and 133 release) and Chrome (133 "dev") on desktop: (A) If I visit http://nih.gov/ in a fresh user profile: I get a network error page. (Firefox Nightly/Release give "The connection was reset | The connection to the server was reset while the page was loading"; Chrome gives "This page isn’t working | nih.gov didn’t send any data. | ERR_EMPTY_RESPONSE". (B) If I type `nih.gov` ("schemeless") and hit enter: then I get automatically upgraded to https and the page loads just fine. (This makes subsequent explicit http loads work fine too, for HSTS reasons noted above.)
Bug 1868167 Comment 7 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
There's been a few changes here: (1) https-first (which had fixed this in Nightly) no longer helps here anymore, as of bug 1919544 (2) ...but this also fails in Chrome nowadays, if I perform the exact same steps and start in the same fresh-user-profile state. I don't know for sure if that's a change in Chrome's behavior or a change in the site or a change in testing methodology. To actually test here, it's important to start with a fresh user-profile, because the HTTPS version of the NIH website sends a HSTS header which forces the browser to auto-upgrade any future http URLs to be https. So as soon as you actually visit the https site, then you'll get expected-results from that point onwards (regardless of browser). So that's why you have to start with a fresh user-profile here. In Chrome, the easiest way to do that is to click the "user-profile menu" just to the left of their 3-dot-menu button, and then choose "Open Guest Profile". Comparing Firefox (135 Nightly and 133 release) and Chrome (133 "dev") on desktop: (A) If I manually type http://nih.gov into the URL bar in a fresh user profile: I get a network error page. (Firefox Nightly/Release give "The connection was reset | The connection to the server was reset while the page was loading"; Chrome gives "This page isn’t working | nih.gov didn’t send any data. | ERR_EMPTY_RESPONSE". (B) If I click comment 0's link to http://nih.gov in a fresh user profile: I get a network error page (same as described above) (C) If I type `nih.gov` ("schemeless") and hit enter: then I get automatically upgraded to https and the page loads just fine. (This makes subsequent explicit http loads work fine too, for HSTS reasons noted above.)
There's been a few changes here: (1) https-first (which had fixed this in Nightly) no longer helps here anymore, as of bug 1919544 (2) ...but this also fails in Chrome nowadays, if I perform the exact same steps and start in the same fresh-user-profile state. I don't know for sure if that's a change in Chrome's behavior or a change in the site or a change in testing methodology. To actually test here, it's important to start with a fresh user-profile, because the HTTPS version of the NIH website sends a HSTS header which forces the browser to auto-upgrade any future http URLs to be https. So as soon as you actually visit the https site, then you'll get expected-results from that point onwards (regardless of browser). So that's why you have to start with a fresh user-profile here. In Chrome, the easiest way to do that is to click the "user-profile menu" just to the left of their 3-dot-menu button, and then choose "Open Guest Profile". Comparing Firefox (135 Nightly and 133 release) and Chrome (133 "dev") on desktop: (A) If I manually type http://nih.gov into the URL bar in a fresh user profile: I get a network error page. (Firefox Nightly/Release give "The connection was reset | The connection to the server was reset while the page was loading"; Chrome gives "This page isn’t working | nih.gov didn’t send any data. | ERR_EMPTY_RESPONSE". (B) If I click comment 0's link to http://nih.gov in a fresh user profile: I get a network error page (same as described above) (C) If I type `nih.gov` (no http/https, i.e. "schemeless") into the URL bar and hit enter: then I get automatically upgraded to https and the page loads just fine. (This makes subsequent explicit http loads work fine too, for HSTS reasons noted above.)
There's been a few changes here: (1) https-first (which had fixed this in Nightly) no longer helps here anymore, as of bug 1919544 (2) ...but this also fails in Chrome nowadays, if I perform the exact same steps and start in the same fresh-user-profile state. I don't know for sure if that's a change in Chrome's behavior or a change in the site or a change in testing methodology. To actually test here, it's important to start with a fresh user-profile, because the HTTPS version of the NIH website sends a HSTS header which forces the browser to auto-upgrade any future http URLs to be https. So as soon as you actually visit the https site, then you'll get expected-results from that point onwards (regardless of browser). So that's why you have to start with a fresh user-profile here. In Chrome, the easiest way to do that is to click the "user-profile menu" just to the left of their 3-dot-menu button, and then choose "Open Guest Profile". Comparing Firefox (135 Nightly and 133 release) and Chrome (133 "dev") on desktop, I get the same results in all three of these experiments: (A) If I manually type http://nih.gov into the URL bar in a fresh user profile: I get a network error page. (Firefox Nightly/Release give "The connection was reset | The connection to the server was reset while the page was loading"; Chrome gives "This page isn’t working | nih.gov didn’t send any data. | ERR_EMPTY_RESPONSE". (B) If I click comment 0's link to http://nih.gov in a fresh user profile: I get a network error page (same as described above) (C) If I type `nih.gov` (no http/https, i.e. "schemeless") into the URL bar and hit enter: then I get automatically upgraded to https and the page loads just fine. (This makes subsequent explicit http loads work fine too, for HSTS reasons noted above.)
There's been a few changes here: (1) https-first (which had fixed this in Nightly) no longer helps here anymore, as of bug 1919544 (2) ...but this also fails in Chrome nowadays, if I perform the exact same steps and start in the same fresh-user-profile state. (I don't know for sure if that's a change in Chrome's behavior or a change in the site or a change in my testing methodology vs. what I or others were doing previously here.) To actually test here, it's important to start with a fresh user-profile, because the HTTPS version of the NIH website sends a HSTS header which forces the browser to auto-upgrade any future http URLs to be https. So as soon as you actually visit the https site, then you'll get expected-results from that point onwards (regardless of browser). So that's why you have to start with a fresh user-profile here. In Chrome, the easiest way to do that is to click the "user-profile menu" just to the left of their 3-dot-menu button, and then choose "Open Guest Profile". Comparing Firefox (135 Nightly and 133 release) and Chrome (133 "dev") on desktop, I get the same results in all three of these experiments: (A) If I manually type http://nih.gov into the URL bar in a fresh user profile: I get a network error page. (Firefox Nightly/Release give "The connection was reset | The connection to the server was reset while the page was loading"; Chrome gives "This page isn’t working | nih.gov didn’t send any data. | ERR_EMPTY_RESPONSE". (B) If I click comment 0's link to http://nih.gov in a fresh user profile: I get a network error page (same as described above) (C) If I type `nih.gov` (no http/https, i.e. "schemeless") into the URL bar and hit enter: then I get automatically upgraded to https and the page loads just fine. (This makes subsequent explicit http loads work fine too, for HSTS reasons noted above.)