# 포럼을 열면 최근 게시글이 아닌 1일 전 이전 게시글로 이동합니다
**URL:** https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459
**Category:** Bug
**Created:** [4월 11, 2026, 5:50오전 UTC](https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459 "2026-04-11T05:50:13Z")
**Posts on this page:** 1
**Showing post:** 21
### Author:  [@zogstrip](https://meta.discourse.org/u/zogstrip)
#### Post date: [7월 31, 2026, 2:52오후 UTC](https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459/21 "2026-07-31T14:52:56Z")
문제가 [`bfcache-compatible`](https://github.com/discourse/discourse/pull/38763) 헤더에서 발생하는 것 같습니다.
>
>
> Previously, enabling \`cache\_control\_bfcache\_compatibility\` (the experiment curre…ntly running on meta, #38763) made HTML documents storable in the browser HTTP cache, and browsers skip revalidation on history navigations — so back/forward, session restore, and discarded-tab reloads could resurrect a days-old document: stale topic lists that only get older, and logged-in UI shown to logged-out sessions (and vice versa). Reported in https://meta.discourse.org/t/400459.
>
> This change keeps the documents out of shared caches (\`no-cache, private\`), reloads any document that was served from the HTTP cache on a history navigation (navigation entry with \`type === "back\_forward"\` and \`transferSize === 0\` — a forced reload gets type \`"reload"\`, so it cannot loop), and validates the session on \`pageshow\` restores from the back/forward cache, reloading when the logged-in user no longer matches the one the page booted with. Both client-side checks only run when the setting is enabled; the full rationale (browser-engine specifics, why \`transferSize\` rather than \`deliveryType\`, why \`fetch\` rather than \`ajax\`) is in the commit message.
>
> Reproduced and verified end-to-end in Chromium and Firefox: with the setting enabled, \`goBack()\` served \`/latest\` with zero network contact — stale list, wrong login state, and the exact \`403 /u/:username/private-message-topic-tracking-state\` errors from the meta report; with this change the same navigation heals with a single automatic reload, and a control run with the setting disabled behaves as before.
_cc @Falco_
---
_[View the full topic](https://meta.discourse.org/t/opening-forum-goes-to-topics-1-day-ago-or-older-not-recent-topics/400459)._