• Resolved Pratham

    (@pratham2003)


    Hi,

    We run a cache optimize content website with the page’s HTML content stored on local cache servers as well as CDN (edge servers). We still retain the server side processing capability for WP API or other types of AJAX request handlers.

    Does the consent plugin rely on server side processing? (In this implementation I won’t expect it to play along nice with page cache)

    or does that take place via JS -> API calls? (In this implementation I would expect to play nice with page cache)

Viewing 3 replies - 1 through 3 (of 3 total)
  • Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    Hi @pratham2003,

    Complianz is built for use with page caching. The dynamic part of the consent process is clientside, and where needed uses js api calls.

    Let me know if you have any questions!

    Thread Starter Pratham

    (@pratham2003)

    Cool, I have another relevant question if it is an API.
    Is the API standalone (independent of WordPress?) because some WordPress installations have a high initialization time per request (since the plugins & themes are loaded and calling this API per request or visitor would then lead to a bottleneck.

    Another off topic query, I actually stumbled upon Cookiedatabase.org. Is there a dependency on their paid API?

    Plugin Contributor Rogier Lankhorst

    (@rogierlankhorst)

    The only api that is used is the free cookiedatabase.org api, which is used once a week to retrieve cookie descriptions, purposes and services.

    No api is requested during a page request.

Viewing 3 replies - 1 through 3 (of 3 total)

The topic ‘Is this plugin optimized for page cache (html)?’ is closed to new replies.