301 redirection is happening for Clientlibs

Hi Team,

We are facing an issue on a multi‑locale AEM site, where some users from the EU region are seeing broken/distorted pages.

Symptoms

• Browser console shows errors indicating that CSS files are not loading properly
• In the Network tab, we see a 301 redirect happening for a ClientLib CSS URL

Example

Original ClientLib URL:

https://domain.com/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.css

Redirected URL:

https://domain.com/de/etc.clientlibs/site/clientlibs/clientlib-react.lc-e0056d5c22903998fcc41c48a71c217e-lc.min.css

Since /de/etc.clientlibs/... does not exist in AEM, the redirected request ends in a 404, which results in the page breaking.

Observations

• The same behavior is reproducible using a curl request (301 redirect observed)
• There are no references to /de/etc.clientlibs/...:
  • Not in AEM configuration
  • Not in Dispatcher
  • Not in rewrite rules
• The only place where this URL appears is in CDN logs, where it shows cache=pass
• We are not caching anything on AEM CS bundled CDN (Fastly)
• All caching is handled only at the Akamai layer

Current Architecture

AEM as a Cloud Service → Akamai (CDN)

Questions

1. Why is the ClientLib URL being redirected to a locale-specific path (/de/)?
2. Which layer is most likely responsible for this redirect?
   • Browser?
   • AEM (Link Rewriter / i18n / sling mapping)?
   • Dispatcher?
   • Fastly (AEM CS managed CDN)?
   • Akamai?
3. Are there any known configurations or headers (e.g. Content-Language, geo rules, accept-language, SEO redirects) that could cause this behavior for /etc.clientlibs paths?

Any insights or pointers on where to start debugging would be really helpful.

Thanks in advance,
Umesh