Can I use a selector to request a font?

Avatar

Avatar
Springboard
Level 3
jkpanera
Level 3

Likes

18 likes

Total Posts

107 posts

Correct reply

2 solutions
Top badges earned
Springboard
Establish
Validate 10
Validate 1
Ignite 5
View profile

Avatar
Springboard
Level 3
jkpanera
Level 3

Likes

18 likes

Total Posts

107 posts

Correct reply

2 solutions
Top badges earned
Springboard
Establish
Validate 10
Validate 1
Ignite 5
View profile
jkpanera
Level 3

06-10-2020

Hi guys,

 

We use selectors to "bust caches" on the dispatcher. For example:

 

/content/dam/web-content/homepage/homepage-coffee.jpg.transform/home-hero/image.20200916.jpeg

 

Then when that image gets updated the selector 20200916 updates and the browser requests a new image with the new url.

 

UPDATE: In response to a question: We don't want to clear the cache. We prefer to bust the cache. This way when an asset is updated, the modified date increases and the clients can use that to request a new asset. Then we can set the browser cache time to be unlimited but the new resource will be requested anyway when it is updated. That way, if we update the page, but the font doesn't change, the browser will continue to cache. the font.

 

We'd like to do the same thing for a custom font (yes we have a custom font that we update), but the same selector trick doesn't work.

For example, 

/content/dam/static/fonts/icon-font/icon-font.1234.ttf and /content/dam/static/fonts/icon-font/icon-font.ttf.transform/original/icon-font.20200916.ttf both return a 404.

 

Is there anyway I can make this work?

 

Thanks! 

Accepted Solutions (0)

Answers (2)

Answers (2)

Avatar

Avatar
Boost 100
Level 6
snbaem
Level 6

Likes

119 likes

Total Posts

248 posts

Correct reply

38 solutions
Top badges earned
Boost 100
Springboard
Establish
Validate 25
Validate 10
View profile

Avatar
Boost 100
Level 6
snbaem
Level 6

Likes

119 likes

Total Posts

248 posts

Correct reply

38 solutions
Top badges earned
Boost 100
Springboard
Establish
Validate 25
Validate 10
View profile
snbaem
Level 6

16-11-2020

Noticed same that use of selector gives a 404. Can you see if using a query parameter ?v=123456 (/content/dam/static/fonts/icon-font/icon-font.1234.ttf and /content/dam/static/fonts/icon-font/icon-font.ttf.transform/original/icon-font.ttf?v=1605545369) works for you? Might need to check any node js capabilities to explore this

Avatar

Avatar
Contributor
Level 2
VeenaK
Level 2

Likes

18 likes

Total Posts

15 posts

Correct reply

3 solutions
Top badges earned
Contributor
Shape 1
Give Back
Boost 5
Boost 3
View profile

Avatar
Contributor
Level 2
VeenaK
Level 2

Likes

18 likes

Total Posts

15 posts

Correct reply

3 solutions
Top badges earned
Contributor
Shape 1
Give Back
Boost 5
Boost 3
View profile
VeenaK
Level 2

08-10-2020

Do you have any specific reason for the selector approach? We have many other ways to clear the cache.

 

Could you share the rules written on the disp files for the same?

 

Reference article: https://docs.adobe.com/content/help/en/experience-manager-dispatcher/using/configuring/page-invalida...