初步評估
WP119 首頁 › 修復實驗室公開紀錄

Capability sweep (recipe r62): HTTP links to the site's own address left in content after a move to HTTPS

配方 20261108-sweep-r62 (r62) · 最新一跑 2026-11-11 · 首次發布 2026-11-09 · 更新 2026-11-11 · Capability sweep

站主看到什麼

The site had been switched to HTTPS, but post content still contained HTTP links to the site's own address, which browsers flag as mixed content.

出處：能力掃描（把「修得了什麼」頁上的一項或多項故障植進同一個測試站），沒有單一論壇帖。

測試環境與弄壞後看到什麼

測試站：WordPress 7.1、PHP 8.3。下表是照配方弄壞之後，首頁與登入頁回的 HTTP 狀態。

主機環境首頁登入頁備註
Apache + PHP-FPM200302
Apache + php-cgi (mod_cgid)200302
Apache + mod_php200302
nginx + PHP-FPM200302

每一跑的結局

日期（UTC）主機環境連線模式結局維修站版本備註逐項結果
2026-11-08Apache + PHP-FPMSSHNot detected2.1.438mixedContent: Still present
2026-11-08Apache + php-cgi (mod_cgid)SSHNot detected2.1.438mixedContent: Still present
2026-11-08Apache + mod_phpSSHNot detected2.1.438mixedContent: Still present
2026-11-08nginx + PHP-FPMSSHNot detected2.1.438mixedContent: Still present
2026-11-09nginx + PHP-FPMFTPNot detected2.1.447mixedContent: Still present
2026-11-09Apache + PHP-FPMFTPNot detected2.1.447mixedContent: Still present
2026-11-09Apache + mod_phpFTPNot detected2.1.447mixedContent: Still present
2026-11-09Apache + php-cgi (mod_cgid)FTPNot detected2.1.447mixedContent: Still present
2026-11-10nginx + PHP-FPMFTPRecovered2.1.448mixedContent: Still present
2026-11-10nginx + PHP-FPMFTPRecovered2.1.448mixedContent: Cleared
2026-11-10Apache + PHP-FPMFTPRecovered2.1.448mixedContent: Cleared
2026-11-10Apache + mod_phpFTPRecovered2.1.448mixedContent: Cleared
2026-11-10Apache + PHP-FPMSSHRecovered2.1.448mixedContent: Cleared
2026-11-10Apache + php-cgi (mod_cgid)FTPRecovered2.1.448mixedContent: Cleared
2026-11-11nginx + PHP-FPMFTPRecovered2.1.455mixedContent: Cleared

缺口與修在哪一版

結局不是修好的跑次，都在這裡：改了什麼、修在哪一版、重跑的日期與結局。

發現日主機環境連線模式改了什麼修在哪一版重跑
2026-11-08Apache + PHP-FPMSSHThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page showed "Link security: All content links use a secure connection". The case page now leaves this row out when it cannot tell, and the count is now read correctly.2.1.4482026-11-10 · Recovered
2026-11-08Apache + php-cgi (mod_cgid)SSHThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page showed "Link security: All content links use a secure connection". The case page now leaves this row out when it cannot tell, and the count is now read correctly.2.1.448—
2026-11-08Apache + mod_phpSSHThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page showed "Link security: All content links use a secure connection". The case page now leaves this row out when it cannot tell, and the count is now read correctly.2.1.448—
2026-11-08nginx + PHP-FPMSSHThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page showed "Link security: All content links use a secure connection". The case page now leaves this row out when it cannot tell, and the count is now read correctly.2.1.448—
2026-11-09Apache + PHP-FPMFTPThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page did not show this check. The count is now read correctly. In these runs, write-back also switched the site to HTTP (see the notes).2.1.4482026-11-10 · Recovered
2026-11-09Apache + php-cgi (mod_cgid)FTPThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page did not show this check. The count is now read correctly. In these runs, write-back also switched the site to HTTP (see the notes).2.1.4482026-11-10 · Recovered
2026-11-09Apache + mod_phpFTPThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page did not show this check. The count is now read correctly. In these runs, write-back also switched the site to HTTP (see the notes).2.1.4482026-11-10 · Recovered
2026-11-09nginx + PHP-FPMFTPThe health check could not count the affected links, so the problem was not listed, the links were not changed, and the case page did not show this check. The count is now read correctly. In these runs, write-back also switched the site to HTTP (see the notes).2.1.4482026-11-10 · Recovered
2026-11-10nginx + PHP-FPMFTPThe links were fixed, but write-back switched the whole site back to HTTP because the site address was entered as HTTP when the case was opened. Write-back now keeps HTTPS in this case.2.1.4512026-11-11 · Recovered

對到的故障項目

補充

The 2026-11-08 runs and the later 2026-11-10 runs entered the site address as HTTPS when the case was opened. The 2026-11-09 runs, the first 2026-11-10 run, and the 2026-11-11 run entered it as HTTP; the 2026-11-11 run checks that write-back keeps HTTPS. After the fix, all four setups were re-run over FTP; over SSH, only Apache + PHP-FPM was re-run. The 2026-11-08 runs used the small test site; the runs from 2026-11-09 on used the copy of the online store test site. WP admin mode was not run in this series.

這一筆的變更

這些是我們測試主機上、某一版、某一天的紀錄，不是對任何網站結果的承諾；其他主機、PHP 與 WordPress 版本的結果可能不同。

初步評估 →