⚡
Edge Playgroundby Judith Medina — Akamai Solutions Engineering
Akamai Cloudlets · Edge Redirector

Every redirect, answered at the edge

Fifteen real use cases — migrations, campaigns, personalisation and operations — solved with one Akamai Cloudlet, no application changes. Click any scenario below and watch it happen live.

Visitor clicks an old link→Akamai edge decides→Instant redirect→Right page, no delay
green page = edge redirectred page = served by origininfo = needs a phone, VPN or config
Live DemoBulk CSV upload, right now
S1P1Migration

Legacy URL migration + query string

A promo page moved after a site restructure. The old URL keeps working and marketing UTMs survive the redirect.

⚙ Technical rule (Akamai config)

URL Path match · Copy Query String · 301

  • S1_legacy_promo: URL Path is /demos/edge-redirector/legacy-promo.html → new-promo.html · 301 · Copy Query String ON
    curl
    # Old URL
    curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/legacy-promo.html' | grep -iE '^(HTTP|location)'
    # Old URL + UTMs
    curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/legacy-promo.html?utm_source=invoice&utm_campaign=autumn' | grep -iE '^(HTTP|location)'
    What to say

    Classic use case, but note the UTMs: the edge copies the incoming query string so analytics attribution is not lost. No origin change was needed.

    S2P1Migration

    Bulk migration from CSV (25 rules)

    A CMS / customer-portal migration map from the SEO team, loaded in one upload instead of 25 tickets.

    ⚙ Technical rule (Akamai config)

    CSV upload · 25 URL Path rules · 301

    • S2_bulk_product_001: (CSV) old/product-001.html → catalog/product.html?id=001 · 301
    • S2_bulk_product_002: (CSV) old/product-002.html → catalog/product.html?id=002 · 301
    • S2_bulk_product_003: (CSV) old/product-003.html → catalog/product.html?id=003 · 301
    • … +22 more rules loaded from CSV
      curl
      # product-001
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-001.html' | grep -iE '^(HTTP|location)'
      # product-002
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-002.html' | grep -iE '^(HTTP|location)'
      # product-003
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-003.html' | grep -iE '^(HTTP|location)'
      # product-004
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-004.html' | grep -iE '^(HTTP|location)'
      # product-005
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-005.html' | grep -iE '^(HTTP|location)'
      # product-006
      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/old/product-006.html' | grep -iE '^(HTTP|location)'
      What to say

      Click 'Test all 25'. Every tile turns green in seconds. In production this is the same flow for thousands of URLs (up to 5,000 rules per policy, split by path into several policies beyond that).

      S3P2Campaigns

      Vanity URL with relative redirect

      Short URL printed on the energy bill or a QR code: /go/solar.

      ⚙ Technical rule (Akamai config)

      URL Path · Use Relative Redirects · 302

      • S3_vanity_solar: URL Path is /demos/edge-redirector/go/solar → /demos/edge-redirector/campaigns/solar.html · 302 · Use Relative Redirects · Copy QS ON
        curl
        # /go/solar
        curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/solar/' | grep -iE '^(HTTP|location)'
        # /go/solar?src=qr
        curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/solar/?src=qr' | grep -iE '^(HTTP|location)'
        What to say

        Look at the curl output: the Location header is relative. The same rule works on every hostname and protocol that uses this shared policy.

        S4P1Campaigns

        Scheduled campaigns: active, future, expired

        Seasonal campaigns switch themselves on and off: autumn is live, winter has not started, summer has ended.

        ⚙ Technical rule (Akamai config)

        Start / end dates per rule · 302

        • S4_autumn_active: URL Path /go/autumn → campaigns/autumn.html · 302 · Start 2026-09-01 · End 2026-12-31
        • S4_winter_future: URL Path /go/winter → campaigns/winter.html · 302 · Start 2026-12-01 · End 2027-02-28
        • S4_summer_expired: URL Path /go/summer → campaigns/summer.html · 302 · Start 2026-06-01 · End 2026-08-31
        summer
        autumn
        winter
        today
        May 2026Mar 2027

        The same pricing URL routes business and home customers to their tariffs based on ?plan=.

        ⚙ Technical rule (Akamai config)

        Edit the dates in the policy if you present outside this window.

          curl
          # /go/autumn (active)
          curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/autumn/' | grep -iE '^(HTTP|location)'
          # /go/winter (future)
          curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/winter/' | grep -iE '^(HTTP|location)'
          # /go/summer (expired)
          curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/summer/' | grep -iE '^(HTTP|location)'
          What to say

          Three rules exist in the policy, but only the one inside its date window fires. The other two fall through to the origin. Nobody has to remember to switch campaigns off.

          S5P1Personalisation

          Query string routing

          URL Path + Query String match · 302

          • S5_plan_business: URL Path pricing.html AND Query String plan=business → pricing-business.html · 302
          • S5_plan_home: URL Path pricing.html AND Query String plan=home → pricing-home.html · 302
            curl
            # ?plan=business
            curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/pricing.html?plan=business' | grep -iE '^(HTTP|location)'
            # ?plan=home
            curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/pricing.html?plan=home' | grep -iE '^(HTTP|location)'
            # no parameter
            curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/pricing.html' | grep -iE '^(HTTP|location)'
            What to say

            Same URL, three outcomes, decided at the edge. The request without a parameter reaches the origin's generic page.

            S6P1Personalisation

            Cookie-based A/B or segment routing

            Customers in variant B (or a logged-in segment) are sent to a different offers page, with no code in the CMS.

            ⚙ Technical rule (Akamai config)

            URL Path + Cookie match · 302

            • S6_cookie_variant_b: URL Path offers.html AND Cookie er_variant=b → offers-b.html · 302
            Cookie
              curl
              # with cookie er_variant=b
              curl -sI -H 'Cookie: er_variant=b' 'https://edge-playground.magicnest.site/demos/edge-redirector/offers.html' | grep -iE '^(HTTP|location)'
              # without cookie
              curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/offers.html' | grep -iE '^(HTTP|location)'
              What to say

              Use the Set/Clear buttons to change the cookie, then click Test in place (or Open in new tab) — the same URL now answers differently. That's A/B testing or segmentation without touching the application.

              S7P2Personalisation

              Language routing (Accept-Language)

              Visitors whose browser prefers Spanish land on the Spanish welcome page.

              ⚙ Technical rule (Akamai config)

              URL Path + Request Header match (wildcard) · 302

              • S7_lang_es: URL Path welcome.html AND Request Header Accept-Language matches es* → es/welcome.html · 302
                curl
                # Accept-Language: es-ES
                curl -sI -H 'Accept-Language: es-ES,es;q=0.9' 'https://edge-playground.magicnest.site/demos/edge-redirector/welcome.html' | grep -iE '^(HTTP|location)'
                # Accept-Language: en-GB
                curl -sI -H 'Accept-Language: en-GB,en;q=0.9' 'https://edge-playground.magicnest.site/demos/edge-redirector/welcome.html' | grep -iE '^(HTTP|location)'
                What to say

                Your browser is in Spanish, so the edge sent you to /es/. The 'test in place' button also sends English to show the negative case.

                S8P3Personalisation

                Custom header routing (partners / apps)

                Partner integrations or the mobile app send X-Client-Type: partner and get partner documentation.

                ⚙ Technical rule (Akamai config)

                URL Path + Request Header match · 302

                • S8_partner_header: URL Path docs.html AND Request Header X-Client-Type is partner → docs-partner.html · 302
                  curl
                  # X-Client-Type: partner
                  curl -sI -H 'X-Client-Type: partner' 'https://edge-playground.magicnest.site/demos/edge-redirector/docs.html' | grep -iE '^(HTTP|location)'
                  # no header
                  curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/docs.html' | grep -iE '^(HTTP|location)'
                  What to say

                  Any request header can drive the decision: app version, partner id, internal traffic flags.

                  S9P2Personalisation

                  Device routing (mobile)

                  Mobile visitors go to the app landing page. Desktop visitors stay on the web page.

                  ⚙ Technical rule (Akamai config)

                  URL Path + Device Characteristics (is_mobile) · 302

                  • S9_mobile: URL Path app.html AND Device Characteristics Is Mobile = true → app-mobile.html · 302
                  Scan with a phone to test the mobile redirect.
                    curl
                    # this browser
                    curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/app.html' | grep -iE '^(HTTP|location)'
                    What to say

                    Open DevTools device mode, or scan the QR code with your phone. The edge detects the device and redirects. Desktop falls through to the origin.

                    S10P3Personalisation

                    Country routing (User Location)

                    Visitors from Spain get the Spanish store; everyone else gets the international store.

                    ⚙ Technical rule (Akamai config)

                    URL Path + User Location country · 302

                    • S10_geo_es: URL Path store.html AND User Location Country is Spain → store-es.html · 302
                      curl
                      # this location
                      curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/store.html' | grep -iE '^(HTTP|location)'
                      What to say

                      Presenting from Spain, you are redirected. Ask someone on a VPN in another country to try it for the negative case.

                      S11P2Advanced

                      Regex rewrite with capture groups

                      A whole legacy URL structure (/blog/YYYY/MM/slug) is rewritten to the new /news model with one rule.

                      ⚙ Technical rule (Akamai config)

                      URL Regular Expression · \1 \2 \3 substitutions · 301

                      • S11_regex_blog: URL Regex https?://[^/]+/demos/edge-redirector/blog/(\d{4})/(\d{2})/([a-z0-9-]+)/?$ → news/article.html?slug=\3&year=\1&month=\2 · 301
                        curl
                        # /blog/2023/05/smart-meters-explained
                        curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/blog/2023/05/smart-meters-explained/' | grep -iE '^(HTTP|location)'
                        # /blog/2024/11/ev-charging-at-home
                        curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/blog/2024/11/ev-charging-at-home/' | grep -iE '^(HTTP|location)'
                        # /blog/archive (no match)
                        curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/blog/archive/' | grep -iE '^(HTTP|location)'
                        What to say

                        One rule covers every blog post. The year, month and slug are captured and reused in the target URL. Regex is powerful but far more expensive than simple matches, so scope it with a path condition.

                        S12P1Operations

                        Maintenance mode with IP exception

                        The customer portal goes into maintenance. Everyone sees the maintenance page except the operations team's IP.

                        ⚙ Technical rule (Akamai config)

                        URL Path contains + IP/CIDR (negated) · 302 · version rollback

                        • S12_maintenance: URL Path contains /demos/edge-redirector/portal/ AND IP/CIDR is NOT 203.0.113.10/32 → maintenance.html · 302 · FIRST rule · only in the 'maintenance ON' version
                        Try it/portal/
                          curl
                          # /portal/
                          curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/portal/index.html' | grep -iE '^(HTTP|location)'
                          What to say

                          I activate the version with the maintenance rule. Please check the portal on your phones: you get maintenance, I still see the portal because my IP is excluded. Then I roll back to the previous version in one click.

                          S13P2Advanced

                          Rule order: first match wins

                          The same vanity URL /go/ev sends existing customers to their offer and everyone else to the generic EV campaign.

                          ⚙ Technical rule (Akamai config)

                          Two rules on the same path · cookie-specific rule first · 302

                          • S13_ev_customer: (rule ABOVE) URL Path /go/ev AND Cookie er_customer=1 → campaigns/ev-customer.html · 302
                          • S13_ev_generic: (rule BELOW) URL Path /go/ev → campaigns/ev.html · 302
                          Cookie
                            curl
                            # customer (cookie er_customer=1)
                            curl -sI -H 'Cookie: er_customer=1' 'https://edge-playground.magicnest.site/demos/edge-redirector/go/ev/' | grep -iE '^(HTTP|location)'
                            # anonymous
                            curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/go/ev/' | grep -iE '^(HTTP|location)'
                            What to say

                            Both rules match /go/ev. Use Set/Clear above to change the cookie, then test again: the specific rule (with the cookie) sits above the generic one, so a returning customer gets their own offer and everyone else gets the generic campaign. Order is part of the logic.

                            S14P3Migration

                            Rebrand: old domain to new brand

                            An acquired or renamed brand's domain is sent, URL by URL, to the new brand site.

                            ⚙ Technical rule (Akamai config)

                            Hostname match · Copy Query String · 301

                            • S14_rebrand: Hostname is old-brand.magicnest.site → rebrand.html · 301 · Copy QS ON (requires the hostname on the property)
                              curl
                              # old-brand host
                              curl -sI 'https://old-brand.magicnest.site/' | grep -iE '^(HTTP|location)'
                              What to say

                              Needs the old hostname on the property with its certificate. Point the old brand domain at Akamai and the edge takes care of the rest.

                              S15P3Advanced

                              Edge vs origin redirect race

                              Why move redirects to the edge? Measure it: the edge answers from the nearest server; the origin adds a round trip.

                              ⚙ Technical rule (Akamai config)

                              Same redirect done at the edge vs at the origin

                              • S15_race_edge: URL Path /race/edge → race/target.html · 302
                              Edge
                              –Origin
                              –

                                curl
                                # /race/edge
                                curl -sI 'https://edge-playground.magicnest.site/demos/edge-redirector/race/edge/' | grep -iE '^(HTTP|location)'
                                What to say

                                Ten requests each way, median shown. Results depend on the network, so present them as illustrative, not as a benchmark.

                                Setup

                                Shared policy ER_Playground, attached in Property Manager to a child rule matching path /demos/edge-redirector/* (plus hostname old-brand.magicnest.site for S14). Rules are evaluated top to bottom, first match wins. S12 lives only in the “maintenance ON” policy version. The 25 S2 rules are uploaded from CSV and appended last.

                                #ScenarioRuleDefinition
                                1S12S12_maintenanceURL Path contains /demos/edge-redirector/portal/ AND IP/CIDR is NOT 203.0.113.10/32 → maintenance.html · 302 · FIRST rule · only in the 'maintenance ON' version
                                2S13S13_ev_customer(rule ABOVE) URL Path /go/ev AND Cookie er_customer=1 → campaigns/ev-customer.html · 302
                                3S13S13_ev_generic(rule BELOW) URL Path /go/ev → campaigns/ev.html · 302
                                4S6S6_cookie_variant_bURL Path offers.html AND Cookie er_variant=b → offers-b.html · 302
                                5S5S5_plan_businessURL Path pricing.html AND Query String plan=business → pricing-business.html · 302
                                6S5S5_plan_homeURL Path pricing.html AND Query String plan=home → pricing-home.html · 302
                                7S7S7_lang_esURL Path welcome.html AND Request Header Accept-Language matches es* → es/welcome.html · 302
                                8S8S8_partner_headerURL Path docs.html AND Request Header X-Client-Type is partner → docs-partner.html · 302
                                9S9S9_mobileURL Path app.html AND Device Characteristics Is Mobile = true → app-mobile.html · 302
                                10S10S10_geo_esURL Path store.html AND User Location Country is Spain → store-es.html · 302
                                11S4S4_autumn_activeURL Path /go/autumn → campaigns/autumn.html · 302 · Start 2026-09-01 · End 2026-12-31
                                12S4S4_winter_futureURL Path /go/winter → campaigns/winter.html · 302 · Start 2026-12-01 · End 2027-02-28
                                13S4S4_summer_expiredURL Path /go/summer → campaigns/summer.html · 302 · Start 2026-06-01 · End 2026-08-31
                                14S3S3_vanity_solarURL Path is /demos/edge-redirector/go/solar → /demos/edge-redirector/campaigns/solar.html · 302 · Use Relative Redirects · Copy QS ON
                                15S15S15_race_edgeURL Path /race/edge → race/target.html · 302
                                16S11S11_regex_blogURL Regex https?://[^/]+/demos/edge-redirector/blog/(\d{4})/(\d{2})/([a-z0-9-]+)/?$ → news/article.html?slug=\3&year=\1&month=\2 · 301
                                17S1S1_legacy_promoURL Path is /demos/edge-redirector/legacy-promo.html → new-promo.html · 301 · Copy Query String ON
                                18S14S14_rebrandHostname is old-brand.magicnest.site → rebrand.html · 301 · Copy QS ON (requires the hostname on the property)
                                …S2S2_bulk_product_001…025CSV upload, 301

                                S15 needs the same redirect configured at the origin on /demos/edge-redirector/race/origin/ → /demos/edge-redirector/race/target.html.