- 🇺🇸United States tstaylor7
In case anyone else ends up here, a simple workaround when a URL or URL pattern is known is to basically copy the disallow_basic_auth_requests service from the basic_auth module in core and check $request->getPathInfo().
Sometimes, for example when we need to use some cache contexts, we want to kill the Page Cache for a given request but we'd love to have the Dynamic Page Cache kicking in. Core provides the page_cache_kill_switch service that should do that but since
#2429617: Make D8 2x as fast: Dynamic Page Cache: context-dependent page caching (for *all* users!) →
(a long time ago) it kills both Page Cache and Dynamic Page Cache.
page_cache_kill_switch:trigger() methodAdd a new service that would allow to only kill the Page Cache.
-OR (harder I guess)-
Add a parameter to the page_cache_kill_switch:trigger() method to define which cache to kill
Needs work
10.1 ✨
Used to track the progress of issues reviewed by the Drupal Needs Review Queue Initiative.
The change is currently missing an automated test that fails when run with the original code, and succeeds when the bug has been fixed.
Not all content is available!
It's likely this issue predates Contrib.social: some issue and comment data are missing.
In case anyone else ends up here, a simple workaround when a URL or URL pattern is known is to basically copy the disallow_basic_auth_requests service from the basic_auth module in core and check $request->getPathInfo().