Upgrade Dispatcher | Community
Skip to main content
robertol6836527
robertol6836527
Level 4
July 20, 2022
Solved

Upgrade Dispatcher

  • July 20, 2022
  • 1 reply
  • 683 views

Good morning,

I would like to upgrade the Dispatcher from version 4.3.3 to version 4.3.5.

 

Reading the documentation I can't understand if I can copy the configurations from version 4.3.3 to version 4.3.5 and everything continues to work unless
DispatcherRestrictUncacheableContent ?

 

Could you tell me if by copying the configuration files from one version to another everything continues to work ?

 

Thanks

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 Jagadeesh_Prakash

@robertol6836527 

 

Please go thought the release note of dispatcher below link

 

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/release-notes.html?lang=en

 

  • DISP-874 - Creates a dispatcher configuration to turn implementation of DISP-818 either On or Off through a flag DispatcherRestrictUncacheableContent. The default value is Off. When On, it removes any caching headers set by mod expires for uncacheable content. This is different from the behavior found in version 4.3.3 (where the default was On) but the same as versions earlier than 4.3.3 (where the default was Off). Keeping DispatcherRestrictUncacheableContent’s default Off is the recommended approach so the browser cache has more flexibility. If, when upgrading from version 4.3.3 to 4.3.4, you wish to keep the same behavior as in version 4.3.3, you must explicitly set DispatcherRestrictUncacheableContent to On.

 

 

1 reply

Jagadeesh_Prakash
Community Advisor
Jagadeesh_PrakashCommunity AdvisorAccepted solution
Community Advisor
July 20, 2022

@robertol6836527 

 

Please go thought the release note of dispatcher below link

 

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/getting-started/release-notes.html?lang=en

 

  • DISP-874 - Creates a dispatcher configuration to turn implementation of DISP-818 either On or Off through a flag DispatcherRestrictUncacheableContent. The default value is Off. When On, it removes any caching headers set by mod expires for uncacheable content. This is different from the behavior found in version 4.3.3 (where the default was On) but the same as versions earlier than 4.3.3 (where the default was Off). Keeping DispatcherRestrictUncacheableContent’s default Off is the recommended approach so the browser cache has more flexibility. If, when upgrading from version 4.3.3 to 4.3.4, you wish to keep the same behavior as in version 4.3.3, you must explicitly set DispatcherRestrictUncacheableContent to On.

 

 

    Terms & ConditionsAccessibility statement

    Loading footer...