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.
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.