Automattic / Automattic/wp-super-cache

Direct cache files for HTTPS pages aren't deleted when hitting the apposite button

Open
#940 1 comment 0 reactions 0 assignees View on GitHub
[Plugin] Super Cache bug
Dominant language
PHP
Stars
436
Forks
130
Avg merge
15h 11m
Merged PRs (30d)
10

Description

Hitting the apposite button to delete direct cache files (see screenshot https://snag.gy/p6IegB.jpg), so under `Settings > Directly cached files` will clear only the HTTP version of the directly cached page; the HTTPS version is never deleted. Currently, we have to delete it via FTP.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start in the WordPress Settings > Directly cached files flow and reproduce the deletion with both HTTP and HTTPS versions of the same page. Trace why the button removes only the HTTP cache entry; done means the button removes both protocol variants, verified by checking that neither direct cache file remains.

Written by the indexing model from the issue text.

Assessment

Tech stack
php, wordpress
Domain
backend, performance
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
45/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.