General Configuration Guideline
Overview
The Cookie Lifetime Extender feature can be implemented with any CDN or web server setup that supports HTTP 301 redirects. It works by issuing a 301 redirect to refresh cookies and extend their lifetime without affecting the user experience.
This guideline provides a general overview of how to configure your CDN or edge network to ensure the JENTIS Cookie Lifetime Extender functions as intended. While specific steps may vary depending on your provider, the general concept remains the same across all CDN environments.
Prerequisites
Before you begin, ensure that:
The JENTIS Cookie Lifetime Extender is correctly enabled in your DCP according to the main configuration guide.
Your CDN or web server allows you to define custom redirect rules (e.g., 301 permanent redirects).
You have administrative access to modify these rules or page rules within your CDN or edge platform.
Example Redirect Rule (Generic)
Below is an example of a redirect configuration that applies to most CDN or reverse proxy environments:
Source URL / Path → Example: /hash
Destination URL → Example: https://hash.example.com/
Redirect Type → 301 Permanent Redirect
Preserve Query String → Enabled
Cache Level → Bypass or standard (depending on CDN)
Tip: In most CDNs, this rule can be defined via a Page Rule, Redirect Rule, or Edge Function configuration.
Verification Steps
After applying the redirect rule:
Open your browser’s developer tools and go to the Network tab.
Trigger an event that invokes the Cookie Lifetime Extender (as defined in your JENTIS setup).
Verify that:
A 301 redirect occurs.
The redirect response leads back to the target URL.
The cookie(s) are correctly updated or extended.
Notes
Always test changes in a staging environment before deploying to production.
If your CDN automatically caches redirects, make sure the rule is set to bypass cache for the extender path.
Refer to your CDN provider’s documentation for exact syntax or configuration UI for redirect rules.
Last updated
Was this helpful?