- 🇦🇹Austria maxilein
See here: https://www.drupal.org/project/drupal/issues/2972483 🐛 Page Cache must respect Vary, otherwise it might serve mismatched responses. Active a module that might help in the meantime: https://www.drupal.org/project/page_cache_vary →
- 🇦🇹Austria maxilein
Maybe we can get a patch to work with many variations as a first step - at least that important functionality works then.
Then we can optimize the many variation if we have a working version. But now we cannot even test it.
Thank you. - 🇦🇹Austria maxilein
The latest merge is in conflict: https://git.drupalcode.org/project/drupal/-/merge_requests/6512/diffs
Conflict: This file was modified in both the source and target branches. Ask someone with write access to resolve it. - 🇦🇹Austria maxilein
Re #217
So perhaps a site with en_EN and fr_FR. A browser comes along and tells the site "Hi i'm en-GB,en-US;q=0.9,en;q=0.8". The site would find out what this will end up as so
en-GB,en-US;q=0.9,en;q=0.8 magic => en_EN, we cache this and threat serve cache asif en_EN. This would mean (at least on the drupal side) only the records for inLang => outLang exist, which are pretty small and we dont end up with loads of difference permutations.
Not entirely sure how we would implement that, but feels like a way to have drupal cache be happy.
The little devil on my shoulder also has a voice though. Which does tell me this is kinda a. can of worms as this could also easily break caching on the caches in front of Drupal, be it varnisch or maybe smoething like cloudflare. That is kinda the scary part. Perhaps contrib is better to have this live, instead of trying to get this into core.
If you think of creating that can of worms, then at least make it configurable and for an admin to see which rules apply.
e.g.
field normalized language: "de" field permuting languages: "de-at,de-de, ..."