Standards and control registry

Method policy, status handling, headers, request and response semantics.

Connector-to-service and relay HTTP interoperability through ASP.NET Core.

Negotiated at managed HTTPS edges where supported; the tunnel is transport-independent.

Gateway preserves cache semantics where policy and rewritten routes allow it.

Persistent relay-to-connector tunnel and binary multiplexed envelopes.

Target validation, path joining, redirect rewriting, and gateway URLs.

Browser-facing URL handling; internal service policy remains normalized URI data.

Private application cookies are rewritten into session-scoped gateway cookies.

Trusted proxy metadata is normalized before security and rate-limit decisions.

Public HTTPS domains rely on managed TLS edge policy and HSTS.

Same-origin checks protect state-changing account endpoints.

Gateway diagnostics identify private applications whose CSP blocks rewritten origins.

Forms, redirects, credentials, streaming responses, and browser request behavior.

Browser and server URL parsing instead of string-concatenated destinations.

Ordinary links, forms, downloads, cookies, and embedded browser application behavior.

Long-lived event streams are forwarded and exercised by the public sandbox.

Public relay and web endpoints negotiate managed TLS.

Compatibility floor depends on the managed edge and host TLS policy.

Connector resolves registered hostnames before establishing the private request.

Resolved address sets are checked against prohibited destinations.

Private targets are expected but remain service-allow-listed.

Link-local and metadata-like destinations are denied by SSRF policy.

Loopback, multicast, link-local, and address classification.

Private IPv6 targets can be classified without granting broad network reach.

SSRF validation rejects special-purpose destinations that should not be proxy targets.

Signed browser sessions and relay capabilities use separate HMAC keys.

Enrollment tokens, connector credentials, session identifiers, and secrets use cryptographic randomness.

Control catalogue for authentication, session, access-control, validation, and logging reviews.

Public-alpha risk review for broken access control, injection, SSRF, and security misconfiguration.

Scheme, hostname, resolved-address, port, and metadata-endpoint restrictions.

Secure, HttpOnly, SameSite cookies, bounded lifetime, and reauthentication policy.

Passwords are salted and hashed with scrypt; plaintext passwords are never stored.

Same-origin enforcement protects state-changing account routes.

Safe event metadata is recorded while credentials, cookies, and bodies are excluded.

Password length, rate limiting, reauthentication, and future MFA direction.

Per-service, per-user, per-session authorization without network-level trust.

Audit event structure, retention planning, and operational review.

Revocation and audit records support investigation workflows.

Named threat addressed by connector target validation and deny-by-default service policy.

Origin validation and SameSite account cookies reduce cross-site state changes.

Connector credentials are hashed server-side and persisted only on the connector host.

Deployment secrets are generated or injected through environment configuration.

Control-plane responses deny untrusted framing.

Connector credentials follow bearer-secret handling rules without being placed in URLs.

Gatehouse currently uses compact HMAC capabilities, not general-purpose JWTs.

Passkeys and phishing-resistant administrator authentication are roadmap items.

Structured relay, connector, API, and audit metadata.

Machine-readable event, heartbeat, grant, and session timestamps.

Trace identifiers cross web, relay, tunnel, and connector boundaries.

Reserved for safe cross-service diagnostic context; secrets are prohibited.

Relay and connector tracing and metric instrumentation are OpenTelemetry-compatible.

Relay and connector containers are built as standard OCI images.

Containers run on ordinary OCI-compatible Linux hosts.

Connector bundle and local demonstration use portable Docker Compose definitions.

Keyboard access, contrast, labels, focus visibility, and responsive text are product targets.

Semantic controls and status announcements supplement native HTML where necessary.

Interaction patterns for dialogs, disclosure controls, navigation, and data views.