Cookies, languages, and deployment boundaries

Three language inputs

Input

Location

Purpose

lang

Login query

Account login UI language; six exact supported values.

locale

Logout body

Account logout/relogin UI language; the same six values, validated after trimming.

locale / Accept-Language

General query/header

Product API language negotiation, supporting en-US/zh-CN; not a substitute for the preceding parameters.

A nonempty Accept-Language takes priority for negotiation; unmatched values fall back to en-US. Only without this header is nonempty query locale validated exactly. Unsupported values return 400 ErrUnsupportedLocale before routing. Login lang=fr-FR does not make query locale=fr-FR valid. Browser error msg currently uses HTTP status text directly. Content-Language alone does not guarantee localized messages.

Frontend deployment modes

In AUTH_MODE=sso, product UserMenu calls product BFF logout and navigates to logout_url. Other modes clear local state and use a CloudSigma bridge or /login. In sso mode, the account site’s LogoutPage reads/ends the UC session and replaces navigation with ‘/login’. Only non-sso mode hands off through product /auth/me, POST /auth/logout, and logout_url. If the current UC session already returns 401, the account logout helper treats it as logged out and sends no further logout write.

If product UC account queries fail, an authenticated product identity may still display profile information, without implying UC administrator privileges. TTL is parsed from configuration and must be positive. Test values of ten minutes or an hour do not establish product defaults.

Evidence status

No new public navigation was added.

Last updated on