Skip to content

[BUGFIX] Render pages for content extraction uncached - #44

Merged
o-ba merged 2 commits into
mainfrom
bugfix/frontend-render-page-cache
Oct 13, 2026
Merged

o-ba merged 2 commits into
mainfrom
bugfix/frontend-render-page-cache

Conversation

@davidsteeb

Copy link
Copy Markdown
Contributor

FrontendPageRenderer renders a page in-process and sent that request through the regular page cache. The output is not what a visitor would get: called from a backend request, TYPO3 has already registered the backend PublicUrlPrefixer, the frontend RequestHandler adds its own, and both prefix file URLs, so they come out as "//fileadmin/...". From CLI the site path is empty and they come out relative. The request carries no cookies, so the page was stored in the page cache and served to every visitor, with every image broken.

The render request now has the page cache disabled: CacheInstruction::disableCache() on TYPO3 13/14, the "noCache" attribute on 12.4. Pages already cached with such URLs stay broken until the page cache is flushed.

The new functional test renders a page through the renderer and asserts that the page cache holds no entry for it. It fails without the change. It needs the pages cache off the NullBackend, and a fixture middleware that adds the testing framework's internal request context, because the json_response middlewares fail on requests that executeFrontendSubRequest() did not build.

Resolves: #43

FrontendPageRenderer sent its in-process request through the regular
page cache. Called from a backend request, the output has file URLs
prefixed twice ("//fileadmin/...") because the backend and the
frontend PublicUrlPrefixer are both registered; from CLI they come
out relative. That page was then served to every visitor.

Disable the page cache for the render request (CacheInstruction on
TYPO3 13/14, the noCache attribute on 12.4).

Resolves: #43
The render bypasses the page cache for reading as well, so a page
cached by a visitor's request is rendered again. A test now covers
that next to the existing write test.

Shorten the docblock of withPageCacheDisabled() to its contract,
reference the issue in the changelog entry and shorten the
description of the test fixture extension.

Related: #43
Signed-off-by: Oliver Bartsch <bo@cedev.de>
@o-ba
o-ba merged commit 051ae4c into main Oct 13, 2026
13 checks passed
@o-ba
o-ba deleted the bugfix/frontend-render-page-cache branch October 13, 2026 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

FrontendPageRenderer stores its render in the page cache

2 participants