An html page is published and is accessible through the dispatcher. A client is trying to access the updated page but is not getting the updated content.
A rule /type “allow” /glob “*.html” is present in the dispatcher /cache /rules configuration
The HTTP header “Cache-Control: max-age=3600” is set for all requests with the html extension
The /invalidate section is not set in the dispatcher configuration
A flush agent is configured on the publish instance
A CDN is serving all static content including html files and was flushed manually
Why does the content fail to update on the client side?

Question

An html page is published and is accessible through the dispatcher. A client is trying to access the updated page but is not getting the updated content.

A rule /type “allow” /glob “*.html” is present in the dispatcher /cache /rules configuration

The HTTP header “Cache-Control: max-age=3600” is set for all requests with the html extension

The /invalidate section is not set in the dispatcher configuration

A flush agent is configured on the publish instance

A CDN is serving all static content including html files and was flushed manually

Why does the content fail to update on the client side?

Wissam Aoun · Accepted Answer

The flush occurred before the content was replicated because there are a lot of items in the queue.

Wissam Aoun · Answer

The file was cached on the client side in the browser cache.

Wissam Aoun · Answer

There is no /invalidate section present in the dispatcher configuration to invalidate the updated content.

Wissam Aoun · Answer

The content is still cached in the dispatcher after the CDN flush.

Question list

List of questions

Question 1

(0)

Question 2

(0)

Question 3

(0)

Question 4

(0)

Question 5

(0)

Question 6

(0)

Question 7

(0)

Question 8

(0)

Question 9

(0)

Question 10

(0)

Related questions

Question 2 - AD0-E106 discussion

Suggested answer: C

0 comments