- 🇺🇸United States greggles Denver, Colorado, USA
The 8.x-2.x branch is no longer supported and the remaining 4.x branches have support for modern Drupal, so I guess closing this as outdated is the most accurate option.
- 🇨🇭Switzerland znerol
Re #21: Fair.
Maybe we need a way to create two (or more) groups of routes. One group is accessed by browsers, others by special clients. Then apply different sets of rules for request processing, content/language negotiation, authentication and caching to each of them.
However, page cache is only effective if it runs before request routing. So maybe the matching needs to happen on a path prefix.
- 🇧🇪Belgium borisson_ Mechelen, 🇧🇪
Using the header and vary on that is very dangerous for cache purposes. It will make very very many variations, which results in bad caching and performance. Not to mention possible memroy issues in caches or high cache trashing.
While this is true for a web-based environment, it is not true for JSON:API.
Quoting @GabeSullice from https://www.drupal.org/project/drupal/issues/2794431#comment-12806367 🌱 [META] Formalize translations support Needs workHowever, JSON API doesn't need to be very concerned about that because JSON API requests are not typically made directly via a browser. Instead, they're most frequently made via JavaScript or some other system where the Accept-Language header can be tightly controlled by a developer.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
Automatically closed - issue fixed for 2 weeks with no activity.
