Facing an very strange issue while upgrading to AEM6.5 | Community
Skip to main content
P
prahlad-dutta
Level 2
May 5, 2020
Solved

Facing an very strange issue while upgrading to AEM6.5

  • May 5, 2020
  • 5 replies
  • 14004 views
Fonts (referenced in clientlib) are not getting rendered via dispatcher, though same is rendering fine on publisher. Below is the log from dispatcher:
---
[]Found farm myproject for myproject-ci-aem65.int.corp
[]checking [/etc.clientlibs/myclientlib/resources/fonts/GloberSemiBold/GloberSemiBold.woff2]
[]cachefile does not exist: /apps/em/dispatcher/cache/etc.clientlibs/myclientlib/resources/fonts/GloberSemiBold/GloberSemiBold.woff2
[]try to create new cachefile: /apps/em/dispatcher/cache/etc.clientlibs/myclientlib/resources/fonts/GloberSemiBold/GloberSemiBold.woff2
[]cache-action for [/etc.clientlibs/myclientlib/resources/fonts/GloberSemiBold/GloberSemiBold.woff2]: CREATE
[]Reusing connection: 10.20.30.40:4503
[]Connected to backend rend01 (10.20.30.40:4503)
[]Adding request header: host
[]Adding request header: Accept
[]Adding request header: Accept-Encoding
[]Adding request header: Accept-Language
[]Adding request header: Cookie
[]Adding request header: Origin
[]Adding request header: Referer
[]Adding request header: User-Agent
[]Adding request header: X-Forwarded-Port
[]Adding request header: X-Forwarded-Proto
[]Adding request header: Via
[]Adding request header: X-Forwarded-For
[]Adding request header: Server-Agent
[]response.status = 204
[]response.headers[Date] = "Tue, 05 May 2020 05:17:38 GMT"
[]response.headers[Cache-Control] = "no-cache"
[]Storing socket for later reuse: 10.20.30.40:4503
[] "GET /etc.clientlibs/myclientlib/resources/fonts/GloberSemiBold/GloberSemiBold.woff2" 204 none [myproject/rend01] 1ms
---
When we hit font file directly (not via site), it get cached properly and started working. Issue seems to be with caching on dispatcher, as dispatcher response status is 204.
 
Any help is highly appreciated!
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 user05162

Can you do the following test:

 

- Allow read access for the "anonymous" user on the /etc directory

- Check if you are able to load the font files.

5 replies

bnb84098
bnb84098
May 5, 2020
Are you able to see the empy directories above GloberSemiBold.woff2 font file ? Is the woff2 font type allowed in your dispatcher rules ? On other clients, we had to add some of these font file types to the dispatcher ALLOW rules.
U
Adobe Employee
user05162Adobe EmployeeAccepted solution
Adobe Employee
May 6, 2020

Can you do the following test:

 

- Allow read access for the "anonymous" user on the /etc directory

- Check if you are able to load the font files.

P
prahlad-duttaAuthor
Level 2
May 8, 2020
No, not still not able to access even though provided read permission to /etc directory
P
prahlad-duttaAuthor
Level 2
May 8, 2020
font folder is looks empty. No font font cache are there. And woff2 font is allowed in dispatcher rule "/0056 { /type "allow" /url "*.woff2" } # enable woff2 "
kautuk_sahni
Community Manager
kautuk_sahniCommunity Manager
Community Manager
May 12, 2020

@joerghoh Any pointer here?

 

Kautuk Sahni
joerghoh
Adobe Employee
joerghohAdobe Employee
Adobe Employee
May 13, 2020

When you request this file via dispatcher, you'll see a request to the AEM publish as well (the request created by the dispatcher); what's the response code of AEM? Is it also 204 (it should)? In case it is, can you go to that publish instance, search this request in the "recent request" view and post the details here? I am especially interested in the servlet handling this request.

Because I am not aware that the ClientLibProxyServlet is able to return the statuscode 204; this statuscode is something I would rather expect in a WebDAV scenario.

    P
    prahlad-duttaAuthor
    Level 2
    May 19, 2020

    Hi @joerghoh,

    Agreed with you point. I have tried to the same steps but not able get any request in publisher end for the fonts. But one strange behavior if I hit the font in a separate tab it downloaded at that time on publisher we get a request for the same. And after when we hit the page through dispatcher font are loading. I mean cache created for the fonts.

    Terms & ConditionsAccessibility statement

    Loading footer...