Baseurl in google-chrome.repo has http instead of https (https is present even in .repo file distributed by Google). It looks like Google redirects all incoming http traffic automatically to https but I think it'd be better to have https in repo file anyway. Version-Release number of selected component (if applicable): 25-2.fc26 How reproducible: Always Steps to Reproduce: 1. Install fedora-workstation-repositories
This message is a reminder that Fedora 26 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 26. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '26'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 26 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Actually there is not a redirect. It just looks like it if you try to use a web browser :-). You might want to close this bug. See wget output below. And I'm 90% sure it ends up using HTTP all the way down to the RPM download. Because I configure it to use a proxy, but my proxy does not support HTTP CONNECT as required for HTTPS. Setting baseurl to use HTTPS causes an error in this configuration, but it works fine with the HTTP baseurl. I'm confused where you would get the idea that Chrome installs a HTTPS baseurl, because that's not what I see. And it's not what you see if you look at the text of /etc/cron.daily/google-chrome Maybe you read a mistaken blog comment that I wrote :-) (and repudiated further down in the thread). https://fedoramagazine.org/third-party-repositories-fedora/#comment-476482 $ wget -H http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml --2018-05-04 19:43:57-- http://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/repomd.xml Resolving dl.google.com (dl.google.com)... 216.58.204.14, 2a00:1450:4009:80c::200e Connecting to dl.google.com (dl.google.com)|216.58.204.14|:80... connected. HTTP request sent, awaiting response... 200 OK Length: 951 [application/octet-stream] Saving to: ‘repomd.xml’ repomd.xml 100%[=======================================================================>] 951 --.-KB/s in 0s 2018-05-04 19:43:57 (78.9 MB/s) - ‘repomd.xml’ saved [951/951]
Fedora 26 changed to end-of-life (EOL) status on 2018-05-29. Fedora 26 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '28'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 28 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.