Dispatcher caching issues with Product Description Pages (PDPs)

This article addresses an issue in AEMaaCS where Product Description Pages (PDPs) are not being cached at the Dispatcher level. The resolution involves implementing the correct rewrite rules to cache PDPs effectively, thus enhancing performance and reducing server load.

Description description

Environment

Adobe Experience Manager as a Cloud Service (AEMaaCS)

Issue/Symptom(s)

Product Description Pages (PDPs) are not being cached at the Dispatcher level. Instead, every request is directed straight to the publisher, leading to inefficiencies and an increased load on the publisher.

Cause

The issue stems from the way PDP paths are rewritten. Specifically, paths starting with /p/ are rewritten without a trailing .html extension, causing caching issues. For example:

Correct Rewrite:

  • Original: /p/product-details-page.html/something
  • Rewritten: /content/product-details-page.html/something.html

Incorrect Rewrite:

  • Original: /p/product-details-page.html/something
  • Rewritten: /content/product-details-page.html/something

The absence of the .html extension in the rewritten path prevents the Dispatcher from caching the page.

Resolution resolution

To resolve this issue, adjust the rewrite rules in the Dispatcher configuration to ensure that a trailing .html extension is included in the rewritten paths.

Steps to adjust Rewrite Rules

  1. Access the Dispatcher configuration:

    • Navigate to the Dispatcher configuration files.
  2. Modify the rewrite rules:

    • Ensure that paths rewritten from /p/ include a trailing .html extension.
  3. Test the configuration:

    • After updating the rules, test to ensure that PDPs are now being cached correctly.
  4. Monitor performance:

    • Observe the load on the publisher to ensure that requests are being cached as expected.
recommendation-more-help
experience-cloud-kcs-help-kbarticles