8839075805
Implements Phases 1-8 of the TFTSR implementation plan. Rust backend (Tauri 2.x, src-tauri/): - Multi-provider AI: OpenAI-compatible, Anthropic, Gemini, Mistral, Ollama - PII detection engine: 11 regex patterns with overlap resolution - SQLCipher AES-256 encrypted database with 10 versioned migrations - 28 Tauri IPC commands for triage, analysis, document, and system ops - Ollama: hardware probe, model recommendations, pull/delete with events - RCA and blameless post-mortem Markdown document generators - PDF export via printpdf - Audit log: SHA-256 hash of every external data send - Integration stubs for Confluence, ServiceNow, Azure DevOps (v0.2) Frontend (React 18 + TypeScript + Vite, src/): - 9 pages: full triage workflow NewIssue→LogUpload→Triage→Resolution→RCA→Postmortem→History+Settings - 7 components: ChatWindow, TriageProgress, PiiDiffViewer, DocEditor, HardwareReport, ModelSelector, UI primitives - 3 Zustand stores: session, settings (persisted), history - Type-safe tauriCommands.ts matching Rust backend types exactly - 8 IT domain system prompts (Linux, Windows, Network, K8s, DB, Virt, HW, Obs) DevOps: - .woodpecker/test.yml: rustfmt, clippy, cargo test, tsc, vitest on every push - .woodpecker/release.yml: linux/amd64 + linux/arm64 builds, Gogs release upload Verified: - cargo check: zero errors - tsc --noEmit: zero errors - vitest run: 13/13 unit tests passing Co-Authored-By: Claude Sonnet 4.6 (1M context) <noreply@anthropic.com>
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;
|