Jurisdiction resolution & content overlay
The precise rules behind the jurisdiction switcher — the resolution priority chain, the hierarchical content-overlay filter, the geo-IP recommendation and the cookie contract.
Resolution priority
Every page request resolves one active jurisdiction by walking this chain and stopping at the first hit:
- 1URL override — a ?j= (or the legacy ?jurisdiction=) query parameter wins for that request.
- 2Cookie — the rpf_j cookie carrying the visitor's chosen market. For a signed-in user it is kept in sync with their account preference.
- 3Default — no jurisdiction (Global): the visitor sees the full catalogue.
The content overlay
Once a jurisdiction is resolved, public list queries apply a hierarchical overlay. A row is shown when it is global (no country), general to the active country, or specific to the active subregion. A whole-country market sees global plus that country's general content; a subregion market (Quebec) additionally sees its own subregion's content. Country-general content is subregion-inclusive — it applies across the whole country. Other markets' rows are excluded.
The overlay applies to published content surfaces only. Draft and archived authoring views are never jurisdiction-filtered, and a directly-navigated detail page is never hidden by jurisdiction — the URL is explicit intent.
Geo-IP recommendation
RPF does not switch your jurisdiction automatically from your location. When you have no market preference and your Cloudflare-provided country (cf-ipcountry) maps to a served market, RPF shows a dismissible banner suggesting it — and nothing more. No third-party geo-IP API is called and no IP address is stored. Dismissing the banner is remembered so you are not asked again.
