Skip to main content
Level 2
Jul 25, 2017 11:48 AM UTC
Solved

AEM 6.3 Proxy ClientLibs didn't work via dispatcher to publisher.

Dear AEM Community,

I finished to update the dispatcher for allow the proxy clientlibs but it didn't load when the domain is pointing to AEM publisher.

Error  404 in browser

Error in AEM publisher

1. The dispatcher allow rule.

/0029 { /type "allow" /url "/etc.clientlibs/*" }

Maybe I miss come configuration.

Any help would be greatly appreciated.

Thanks,

Thomas.

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
cqsapientu69896
cqsapientu69896Accepted solution
Level 4
Sep 7, 2017 6:03 AM UTC

I solved by adding the mapping -

sling:match etc[.]clientlibs/(.+)

sling:internalRedirect /etc.clientlibs/$1

so that it matches only one character - '.' after /etc

Now both /etc/clientlibs and /etc.clientlibs requests return a response.

16 replies

joerghoh
Employee
Jul 26, 2017 5:47 PM UTC

Hi,

if you get this exception on the AEM publish, it's a not an issue with the dispatcher at all, the dispatcher forwards the request to AEM correctly. It's rather an issue on your AEM side.

You wrote, that the under some circumstances (hitting the URL directly) the response was ok and the javascript file has been delivered. Can you elaborate on that and the differences between the working and the non-working scenario?

kind regards,
Jörg

Translate
Feike_Visser1
Employee
Jul 26, 2017 7:59 AM UTC

Can you add clientlibs also to the allowed extensions?

Translate
Level 2
Jul 25, 2017 4:16 PM UTC

Hi @Techaspect Solutions​,

I added into the dispatcher.any before ( rule 0041)  it's worked well for other js/css under /etc/....

I just faced this issue with proxy clientlib. I added your rule (0030) for checking and restarted dispatcher but it's the same.

( Noted that the rule for JS has been added in 0041 but I added it again on 0030 for checking )

The screenshot about the configuration for more details.

I really appreciate your help,

Thanks,

Thomas.

​

Translate
Techaspect_Solu
Level 7
Jul 25, 2017 12:42 PM UTC

Hi tinyt6510512,

Can you try by adding the below rule in ".any" file

-- { /type "allow" /url "*.js"   }

Thanks,

Techaspect Solutions.

Translate
Level 2
Jul 25, 2017 12:21 PM UTC

Hi,

Thanks for your supporting but I tried with anonymous user on publisher ( via IP ) it's worked welll

Thanks,

Thomas.

Translate
Techaspect_Solu
Level 7
Jul 25, 2017 12:13 PM UTC

Hi tinyt6510512,

I think there are no read permissions(/etc/design) for the anonymous user in the publish.

Could you verify the anonymous user permission in the publish server ?

Thanks,

Techaspect Solutions.

Hi tinyt6510512,

I think there are no read permissions(/etc/design) for the anonymous user in the publish.
Could you verify the anonymous user permission in the publish server ?

Thanks,
Techaspect Solutions.
http://www.techaspect.com/

Translate