Skip to content

[FEATURE] Tag-based response cache for GET endpoints (#146)#147

Open
klamparski wants to merge 6 commits into
release/5.0.0from
146-feature-tag-based-response-cache-for-get-endpoints
Open

[FEATURE] Tag-based response cache for GET endpoints (#146)#147
klamparski wants to merge 6 commits into
release/5.0.0from
146-feature-tag-based-response-cache-for-get-endpoints

Conversation

@klamparski

Copy link
Copy Markdown
Collaborator

Closes #146

@klamparski klamparski added this to the 5.0.0 milestone Jul 14, 2026
@klamparski klamparski added the enhancement New feature or request label Jul 14, 2026
… failures

OperationNotAllowedException's constructor could itself throw an unrelated exception (e.g. ArgumentCountError from TYPO3 core internals) whenever LocalizationUtility::translate() failed, masking the real access-denied error - and forced OperationResponseCacheTest::registerFakeTranslation() to fake TYPO3's translation machinery in increasingly TYPO3-version-specific ways (three distinct failure modes across TYPO3 12/13/14 point releases). Falling back to the raw translation key removes both problems at once.
…tibility

SiteMatcher::getRouteCollectionForVeryFirstRequestPattern() called idn_to_ascii() on a site language's host without guarding against an empty value (e.g. a relative site base) - harmless on PHP 8.1-8.3, but PHP 8.4 made idn_to_ascii() throw ValueError on an empty argument. TYPO3 core added the missing guard in 12.4.18; our declared floor, 12.4.16, predates the fix. Bumped cms-core/cms-extbase/cms-frontend/cms-install together to keep the TYPO3 12 distribution's version floor consistent.
@sonarqubecloud

Copy link
Copy Markdown

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

enhancement New feature or request

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant