Cache not cleared for existing 404s

Created on 15 March 2024, 7 months ago

Updated 14 June 2024, 4 months ago

Problem/Motivation

When a URL already has been visited and produces a 404, saving a domain path will not clear the cache for that URL. When the URL is visited again, the 404 persists.

Steps to reproduce

- Ensure page caching is enabled
- Visit a URL: /foo
- Create a new node with a domain path of /foo
- Visit /foo again

Proposed resolution

Implement the same cache tag clearing as core Path entity.

Remaining tasks

User interface changes

API changes

Data model changes

🐛 Bug report

Status

Closed: duplicate

Version

1.0

Component

Code

Created by

🇺🇸United States dabblela

Live updates comments and jobs are added and updated live.

Comments & Activities

Issue created by @dabblela
Comment 7 months ago →
🇺🇸United States dabblela
Comment 7 months ago →
🇺🇸United States dabblela
Status changed to Needs review 7 months ago6:40pm 15 March 2024
Comment 7 months ago →
🇺🇸United States dabblela
Status changed to Closed: duplicate 4 months ago11:45am 14 June 2024
Comment 4 months ago →
🇩🇪Germany webflo
Hello @dabblela, this is a duplicate issue of 🐛 Provide route_math tag invalidation. Needs review . The other issue contains the same patch and a test. Please review. Thanks!

contrib.social Blog FAQ Discussions

Production build 0.71.5 2024