Drupal 10, the latest version of the open-source digital experience platform with even more features, is here.Problem/Motivation
Currently cgit.drupalcode.org domain does serve a valid SSL certificate, which make patching using composer less secure and more difficult specialy in the case of contib profiles composer.json using the patch (row) commit url https://cgit.drupalcode.org/panels/patch/?id=SHA-1
The problem is that a lot of module maintainers do commit directly to the project repository without uploading a patch file to an issue, and composer by default doesn't allow insecure url without a special config [secure-http] in addition the config directive is only avilable to for the Root Package.










Comments
Comment #2
mlhess CreditAttribution: mlhess as a volunteer commentedThere should be a cert here. However, I would reference commits by git hash.
Comment #3
jp.stacey CreditAttribution: jp.stacey at Magnetic Phield commented+1 for this. When anyone - a client, or a potential contributor - follows a cgit link, they get e.g. a Chrome net::ERR_CERT_COMMON_NAME_INVALID error or Firefox SSL_ERROR_BAD_CERT_DOMAIN, and then have to jump through hoops to even see the content. This reflects poorly on Drupal in all sorts of ways.
Comment #4
jp.stacey CreditAttribution: jp.stacey at Magnetic Phield commentedMarking this as a bug as it causes a HTTPS exception in the browser.
Comment #5
SylvainM CreditAttribution: SylvainM at Axess Open Web Services commented+1
Comment #6
Tess BakkerPlease, setup a new valid SSL certificate for cgit.drupalcode.org and dump the wildcard version that is only valid for *.drupal.org
Composer
.. yes, i know, we should use https ..
Firefox
Solution: Allow packages from unsafe locations?!
Comment #7
Tess BakkerChecked with Composer, Firefox and Chromium and the certificate is valid :)