Ideas

Casey_Grimes · ‎06-21-2022

Marketo was recently updated to support setting HTTP headers for landing pages, including setting HSTS. This is great! However, additional standard security headers should be set for Marketo Landing Pages; this is onerous to do and requires proxy work outside of the platform. Would it be possible to add support for the following header items: x-content-type-options referrer-policy x-frame-options content-security-policy permissions-policy Additionally, the following three headers are upcoming and should have future support: cross-origin-embedder-policy cross-origin-opener-policy cross-origin-resource-policy This helps harden security for Marketo landing pages and may be required for infosec reasons.

Casey_Grimes · ‎10-04-2022

Part of Marketo Engage's platform involves encoding tracking email links so the platform can accurately associate email activity with records. However, the method that makes this work involves sending a 302 redirect link without any additional HTTP header content; it defaults to Cloudflare's standard instead. This makes it complicated for technical solution providers to determine safe 302 redirects from Adobe and more problematic unencoded 302 redirect links. Would it be possible to put a custom header for technology providers to check against? I'm thinking something as plain as "x-generated-by: adobe-marketo-engage" or similar; this is also straightforward to implement on the CF side.

Ideas

Live Chat Support using Dynamic Chat

GDPR & reporting: Link scanner-proof email click d...

Pardot is filtering out bot clicks, why won't Mark...

Add Additional HTTP Header Support for Landing Pages

Provide Identifier in HTTP Header When Email Redirect Links Are Generated in Cloudflare