The configuration is resolved from the current URI. To be precise, the first path segment of the URI is used to find a matching config name which will be returned.

If the URI doesn't contain such a valid name – which is tha case when a site uses a domain + mapping with a handlePrefix – the correct configuration is not resolved.

Travel Demo uses a custom config named travel:

• This does not work https://demopublic.magnolia-cms.com/members/registration.html
• This works https://demopublic.magnolia-cms.com/travel/members/registration.html

Suggested solutions

1. Deprecate DefaultConfigurationResolver and use the info.magnolia.module.site.SiteManager by default to resolve the config
   • Might break clients installation because their config resolution might rely on old one
2. Maintain the old ConfigurationResolver and a new one (info.magnolia.module.publicuserregistration.configuration.DelegatingConfigurationResolver) that is aware of both resolver
   • Maintains backwards compat.