Commit d4f88c1
committed
deploy: be more careful when auto-upgrading from HTTP -> HTTPS
Since we play dirty tricks with `/etc/hosts` before running the
Playwright tests in order to side-step Cloudflare's caches, we need to
avoid using HTTPS for git-scm.com because the certificate would not be
liked by Playwright. The symptom is:
Error: page.goto: net::ERR_CERT_COMMON_NAME_INVALID at https://git-scm.com/
The most likely explanation is that GitHub, when trying to verify the
DNS settings, realizes that the actual DNS entries by Cloudflare do
_not_ point to GitHub's servers and therefore refuses to get a custom
certificate from Let's Encrypt for git-scm.com. As a consequence, the
certificate it provides does not cover that domain, it only covers
*.github.io.
Let's just leave http://git-scm.com/ alone.
Signed-off-by: Johannes Schindelin <[email protected]>1 parent b99865e commit d4f88c1
1 file changed
+4
-1
lines changed| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
| |||
196 | 196 | | |
197 | 197 | | |
198 | 198 | | |
199 | | - | |
| 199 | + | |
| 200 | + | |
| 201 | + | |
| 202 | + | |
200 | 203 | | |
201 | 204 | | |
202 | 205 | | |
| |||
0 commit comments