初期診断
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.

出典：能力スイープ（「復旧できること・できないこと」ページに掲載されている問題を 1 つ以上、1 つのテストサイトに仕込んだもの）。単一のフォーラムスレッドはありません。

テスト構成と、障害再現後に観測した状態

テストサイト：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 のバージョンが異なれば結果も異なることがあります。

初期診断 →