dtoro
d4d99a7473
Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
56 lines
2.1 KiB
TypeScript
56 lines
2.1 KiB
TypeScript
/**
|
|
* Options for configuring how {@link getPublicSuffix} behaves.
|
|
* @public
|
|
*/
|
|
export interface GetPublicSuffixOptions {
|
|
/**
|
|
* If set to `true` then the following {@link https://www.rfc-editor.org/rfc/rfc6761.html | Special Use Domains} will
|
|
* be treated as if they were valid public suffixes ('local', 'example', 'invalid', 'localhost', 'test').
|
|
*
|
|
* @remarks
|
|
* In testing scenarios it's common to configure the cookie store with so that `http://localhost` can be used as a domain:
|
|
* ```json
|
|
* {
|
|
* allowSpecialUseDomain: true,
|
|
* rejectPublicSuffixes: false
|
|
* }
|
|
* ```
|
|
*
|
|
* @defaultValue false
|
|
*/
|
|
allowSpecialUseDomain?: boolean | undefined;
|
|
/**
|
|
* If set to `true` then any errors that occur while executing {@link getPublicSuffix} will be silently ignored.
|
|
*
|
|
* @defaultValue false
|
|
*/
|
|
ignoreError?: boolean | undefined;
|
|
}
|
|
/**
|
|
* Returns the public suffix of this hostname. The public suffix is the shortest domain
|
|
* name upon which a cookie can be set.
|
|
*
|
|
* @remarks
|
|
* A "public suffix" is a domain that is controlled by a
|
|
* public registry, such as "com", "co.uk", and "pvt.k12.wy.us".
|
|
* This step is essential for preventing attacker.com from
|
|
* disrupting the integrity of example.com by setting a cookie
|
|
* with a Domain attribute of "com". Unfortunately, the set of
|
|
* public suffixes (also known as "registry controlled domains")
|
|
* changes over time. If feasible, user agents SHOULD use an
|
|
* up-to-date public suffix list, such as the one maintained by
|
|
* the Mozilla project at http://publicsuffix.org/.
|
|
* (See {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.3 | RFC6265 - Section 5.3})
|
|
*
|
|
* @example
|
|
* ```
|
|
* getPublicSuffix('www.example.com') === 'example.com'
|
|
* getPublicSuffix('www.subdomain.example.com') === 'example.com'
|
|
* ```
|
|
*
|
|
* @param domain - the domain attribute of a cookie
|
|
* @param options - optional configuration for controlling how the public suffix is determined
|
|
* @public
|
|
*/
|
|
export declare function getPublicSuffix(domain: string, options?: GetPublicSuffixOptions): string | undefined;
|