Expand my Community achievements bar.

Guidelines for the Responsible Use of Generative AI in the Experience Cloud Community.
SOLVED

allowProxy Clientlibs

Avatar

Level 6

How does by adding allow proxy for clientlibs, css, js will be loaded on dispatcher or publisher?

Searched for the internal working of that but didn't found any source.

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

@Keerthi0555 

 

Allowing proxies for ClientLibs means configuring AEM to serve these resources through a proxy URL pattern. This is typically done to namespace and manage access to these resources efficiently. For example, you might serve all client-side resources under a path like /etc.clientlibs/ which is proxied to a more accessible path like /libs/.

 

 

 

View solution in original post

3 Replies

Avatar

Community Advisor

Client libraries under `/apps` should be exposed via `/etc.clientlibs` using the `allowProxy` property. Since `/apps` paths are generally blocked by dispatcher filters for security reasons, without `allowProxy`, this would result in a 404 error. Same applied for publisher but via permissions. To resolve this, clientlibs can be safely exposed from `/apps` through `/etc.clientlibs` using the `allowProxy` property.



Arun Patidar

Avatar

Community Advisor

Here is some documentation, explaining what Arun already mentioned: https://experienceleague.adobe.com/en/docs/experience-manager-65/content/implementing/developing/int... In case is useful. 

 

Hope this helps

 

 



Esteban Bustamante

Avatar

Correct answer by
Community Advisor

@Keerthi0555 

 

Allowing proxies for ClientLibs means configuring AEM to serve these resources through a proxy URL pattern. This is typically done to namespace and manage access to these resources efficiently. For example, you might serve all client-side resources under a path like /etc.clientlibs/ which is proxied to a more accessible path like /libs/.