Automattic / Automattic/wp-super-cache

_escaped_fragment_= issue

Open
#933 0 comments 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

url: http://www.example.com/test.html
This file has not an ajax content and size 10kb

ajax url: http://www.example.com/test.html?_escaped_fragment_=
this file has an ajax content and size 200kb

When a search engine enter in to ajax url, the super cache file(10kb) is deleted and updated as ajax html file cache. The new size of the cache is 200kb.

Contributor guide

No contributing guide indexed for this repository

Research direction

Start by reproducing the behavior with the two URLs in the report and compare the cached 10KB non-AJAX response with the 200KB _escaped_fragment_= response. The issue names no files or tests and does not define the desired cache behavior, so clarify expected cache retention before implementation.

Written by the indexing model from the issue text.

Assessment

Tech stack
php
Domain
performance
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.