What is HTTPS Redirect & Security Defaults?
Port-80-to-443 redirection with HSTS/CSP inherited from the edge. Generated apps get transport security by platform default, not per-project configuration.
Related terms
Traefik Reverse Proxy
The edge router in front of BYOB services: web/websecure entrypoints, Docker and file providers, automatic HTTPS redirects. One proxy terminates TLS and routes every workspace, preview, and API.
HTTPS
Encrypted HTTP via TLS, a lightweight ranking signal and a trust requirement. Mixed HTTP resources on HTTPS pages still split signals and trigger browser warnings.
Security Headers
HTTP response headers (CSP, HSTS, frame options) hardening a deployed site. Edge hosts should set sensible defaults; generated apps inherit them without per-project configuration.
Svelte Runes
The `$state`, `$derived`, `$effect`, and `$props` primitives powering Svelte 5 reactivity. Runes are mandatory in generated code: explicit, compilable, and consistent across every component.
File-Based Routing
Pages defined by file location: `+page.svelte` renders, `+layout.svelte` wraps, `+server.js` serves data. The route tree is the app map — no separate router config to drift.
Load Function
Server-side data loading for a route before it renders. Load on the server for content crawlers and users need immediately; reach for client fetching only for interactive extras.