Caching Secure Pages | Community
Skip to main content
A
arvind-1
New Participant
March 17, 2023
Solved

Caching Secure Pages

  • March 17, 2023
  • 1 reply
  • 795 views

Hi Team,

 

1) How dispatcher understands that page for which request is coming is logged in / secured /authenticated page? Is there any example? or we do it through some code?

2) How Dispatcher determines that since it is secure PAGES; its not candidate for caching ?

3) How we make dispatcher to cache secure pages as well? 

 

 

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 nitesh_kumar-1

Hi @arvind-1 ,

 

here are some high-level details on how the dispatcher validates and caches secure content.

  • Dispatcher determines that the requested content is cached and valid.
  • Dispatcher sends a request message to the render. The HEAD section includes all of the header lines from the browser request.
  • The render calls the auth checker servlet to perform the security check and responds to Dispatcher. The response message includes an HTTP status code of 200 to indicate that the user is authorized.
  • Dispatcher sends a response message to the browser that consists of the header lines from the render response and the cached content in the body.

To implement permission-sensitive caching, perform the following tasks:

  • Develop a servlet that performs authentication and authorization
  • Configure the Dispatcher

More details about implementation can be found in the documentation below

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/permissions-cache.html?lang=en 

 

Hope this helps!

 

Regards,

Nitesh

1 reply

nitesh_kumar-1
nitesh_kumar-1Accepted solution
Employee
March 17, 2023

Hi @arvind-1 ,

 

here are some high-level details on how the dispatcher validates and caches secure content.

  • Dispatcher determines that the requested content is cached and valid.
  • Dispatcher sends a request message to the render. The HEAD section includes all of the header lines from the browser request.
  • The render calls the auth checker servlet to perform the security check and responds to Dispatcher. The response message includes an HTTP status code of 200 to indicate that the user is authorized.
  • Dispatcher sends a response message to the browser that consists of the header lines from the render response and the cached content in the body.

To implement permission-sensitive caching, perform the following tasks:

  • Develop a servlet that performs authentication and authorization
  • Configure the Dispatcher

More details about implementation can be found in the documentation below

https://experienceleague.adobe.com/docs/experience-manager-dispatcher/using/configuring/permissions-cache.html?lang=en 

 

Hope this helps!

 

Regards,

Nitesh

    Terms & ConditionsAccessibility statement

    Loading footer...