clientlibrarymanager.js accessible on Author Server but not Publish server ? | Community
Skip to main content
July 22, 2020
Solved

clientlibrarymanager.js accessible on Author Server but not Publish server ?

  • July 22, 2020
  • 5 replies
  • 1463 views

Hi All,

The first link below is working correctly but the second link below says Not Found :-

https://author-6.5.2/etc.clientlibs/clientlibs/granite/clientlibrarymanager.js
https://publish-6.5.2/etc.clientlibs/clientlibs/granite/clientlibrarymanager.js

I have checked that allowProxy is true in /libs/clientlibs/granite/clientlibrarymanager on Both servers.

Please can you advise why second link above says Not Found ?

Thank you for your time and advise.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by sunjot16

On the publish server, are you able to reproduce the issue, when you bypass the dispatcher(i.e., access the publish server using its host & port directly)?

a) If not, then enable DEBUG logging for dispatcher, and see which filter is blocking the request. You can then allow this request to go through dispatcher.

 

b) If it's still reproducible, invalidate cache & rebuild clientlibs via File System, as per [1], clear all browser cache & cookies, close all browser tabs & windows, open a new one in Incognito mode, and then verify whether the issue is still reproducible.

 

Hope it helps !!

 

 

[1] https://helpx.adobe.com/experience-manager/kb/How-to-force-a-recompilation-of-all-Sling-scripts-jsps-java-sightly-on-AEM-6-4.html

5 replies

Adobe Employee
July 22, 2020

Can you check if the dispatcher is blocking this URL on the publish tier? If that's, not the case, try rebuilding clientlibs to clear the cache. 

 

[1] https://helpx.adobe.com/experience-manager/kb/How-to-force-a-recompilation-of-all-Sling-scripts-jsps-java-sightly-on-AEM-6-4.html

ChitraMadan
Community Advisor
Community Advisor
July 22, 2020

Hi @james-collett ,

 

It will be worth to check the permissions for anonymous users on publishers.

Most of the time 404 issues on publishers are related to permissions for anonymous users.

 

Try giving read access on /etc, if it is already not there.

 

 

BrianKasingli
Community Advisor and Adobe Champion
Community Advisor and Adobe Champion
July 22, 2020

@james-collett Also, does your Dispatcher configuration, https://publish-6.5.2/etc.clientlibs/clientlibs/granite/clientlibrarymanager.js, allow /etc.clientlibs/* ?

vanegi
Adobe Employee
Adobe Employee
July 22, 2020

Hi @james-collett,

Please try this solution out on your publish instance:

1. Go to http://hostport/system/console/configMgr

2. Search for and open Apache Sling Authentication Service

3. Add these two entries to the sling.auth.requirements

-/etc.clientlibs

-/etc/clientlibs/granite

4. After changing the property, restart the bundle http://host:port/system/console/bundles/org.apache.sling.auth.core

 

Thanks!!

sunjot16
Adobe Employee
sunjot16Adobe EmployeeAccepted solution
Adobe Employee
July 23, 2020

On the publish server, are you able to reproduce the issue, when you bypass the dispatcher(i.e., access the publish server using its host & port directly)?

a) If not, then enable DEBUG logging for dispatcher, and see which filter is blocking the request. You can then allow this request to go through dispatcher.

 

b) If it's still reproducible, invalidate cache & rebuild clientlibs via File System, as per [1], clear all browser cache & cookies, close all browser tabs & windows, open a new one in Incognito mode, and then verify whether the issue is still reproducible.

 

Hope it helps !!

 

 

[1] https://helpx.adobe.com/experience-manager/kb/How-to-force-a-recompilation-of-all-Sling-scripts-jsps-java-sightly-on-AEM-6-4.html