Core Structure
Inbound
Resolves locale, pathname, and related request context.
The resolution flow consists of two complementary parts:
Locale Resolution
Locale resolution determines the active locale based on one or more ordered locale source types.
These sources participate in the resolution process in the following order:
path | host | query | cookie | detected
For configuration details, see: localeSources
The cookie source participates in resolution only when cookie.enabled is true. This option defaults to false, so locale cookies are not read by default.
When using the host source, the left-most subdomain (e.g. en in en.example.com) is used as the locale candidate.
Normalization
Resolved locale candidates are normalized and aligned to supportedLocales.
An exact match is attempted first; if none is found, resolution falls back to the base language.
Path Resolution
Path resolution determines the effective pathname of the current request based on the configured path rules.
See: Path
Integration
In each runtime environment, Intor provides create-intor-handler to handle Inbound Routing.
For framework-specific integration details, see Frameworks