Skip to main content
Version: 3.14 Beta (Latest)

Dynamic config URLs need an origin list or an anchored pattern

This matters only if your app config sets dangerouslyUseDynamicConfig.enabled: true, so that a ?configUrl= link can load a different configuration.

A dynamic config document controls the data sources and which extensions and modes the viewer loads, so 3.14 checks the URL more strictly. A configUrl that 3.13 accepted can now be refused, and the viewer then starts with its built-in configuration. A refusal caused by the configuration itself, such as a missing gate or a pattern without ^, logs an error that starts with dangerouslyUseDynamicConfig: Refusing to load ?configUrl=. A URL that an anchored pattern simply doesn't match is ignored without a message, which is what happens to a pattern written for relative values (below).

What changed​

3.133.14
What is checkedthe raw configUrl valuethe absolute URL the browser will fetch
No regexevery URL acceptedrefused, unless origins is set
regex without a leading ^matched anywhere in the URLrefused
regex with the m flagallowedrefused
originsnot availablethe URL's origin must be in the list
Schemes other than http:/https:passed to fetchrefused

When both origins and regex are set, both must pass.

Update your configuration​

Prefer origins. It compares the URL's origin exactly, so there is no pattern to get wrong.

A catch-all pattern:

// 3.13
dangerouslyUseDynamicConfig: { enabled: true, regex: /.*/ },

// 3.14: list the origins that serve your config documents
dangerouslyUseDynamicConfig: { enabled: true, origins: ['https://config.hospital.com'] },

If you must accept any URL, use the anchored regex: /^/. This lets anyone who can send a user a link choose the code the viewer loads, so avoid it.

A pattern that names a host:

// 3.13: also matched https://evil.example/?x=hospital.com
dangerouslyUseDynamicConfig: { enabled: true, regex: /hospital\.com/ },

// 3.14
dangerouslyUseDynamicConfig: { enabled: true, origins: ['https://hospital.com'] },
// or, to also limit the path
dangerouslyUseDynamicConfig: { enabled: true, regex: /^https:\/\/hospital\.com\/configs\// },

A pattern written for relative values:

// 3.13: matched ?configUrl=/configs/site.json
dangerouslyUseDynamicConfig: { enabled: true, regex: /^\/configs\// },

// 3.14: the pattern sees https://viewer.hospital.com/configs/site.json
dangerouslyUseDynamicConfig: {
enabled: true,
regex: /^https:\/\/viewer\.hospital\.com\/configs\//,
},

See dangerouslyUseDynamicConfig in Configuration files for the full rules.