English stays the default; Czech is a full translation. Only the app chrome is translated - notes and generated decks keep their own language, which is a core feature, not a setting. i18n - lib/i18n-dict.ts: flat en/cs dictionaries (441 keys each), translate() and translatePlural() with real Czech plural rules (1 sada / 2-4 sady / 5+ sad). English is the default and the fallback for a missing key. - lib/i18n.ts: browser store (freezmo.locale.v1), useI18n() hook, and the x-freezmo-locale header. The hook's t/plural are bound to the locale React is rendering with, so the first client render matches the server HTML and then re-renders in the stored language; module-level t is only for event handlers and non-React helpers. - <html lang> follows the choice (inline script + setLocale). UI - Settings -> Language segmented control (English / Cestina), plus an EN/CS button on the key gate for first run. - Every screen translated: sidebar, header, tab bar, library, deck cards, folder bar, create flow, all seven activities, study chrome, results, settings + health panel, API-key gate and help, install sheet, offline and the deck-not-found page. - Plural-aware counts everywhere (decks, folders, activities, runs, photos, documents, pages, words, wrong attempts). Server - API routes and guards (generate, grade, health, http-guard, rate-limit, ollama error mapping) answer in the request's language, so error cards and the health panel never fall back to English mid-sentence. Fixes - A hydration mismatch when a non-default locale was stored silently dropped the .dark class after hydration; render-time t() is now bound to the hook's locale (UploadScreen.describeExtraction, ResultsScreen.answerFor, DeckCard's folder fallback). - Bumped the service worker cache to freezmo-v4 for this deploy. Tests: i18n 27/27 (gate toggle, persistence, html lang, Czech plurals, settings switch) and a rebuilt regression suite 72/72 (English default, library, create, all 7 activity types, results, settings, install sheet, offline, PWA, security, Czech smoke).
92 lines
3.3 KiB
TypeScript
92 lines
3.3 KiB
TypeScript
import { LOCALE_HEADER, normaliseLocale, translate } from "./i18n-dict";
|
|
|
|
/**
|
|
* Small server-side guards shared by the API routes.
|
|
*
|
|
* Freezmo is a self-hosted app with no accounts, so the realistic threats are
|
|
* (a) a hostile page in the user's browser poking the local server, (b) huge
|
|
* bodies exhausting memory, and (c) odd values ending up in outbound headers.
|
|
*/
|
|
|
|
/** The language this request asked for (browsers send x-freezmo-locale). */
|
|
export function requestLocale(request: Request) {
|
|
return normaliseLocale(request.headers.get(LOCALE_HEADER));
|
|
}
|
|
|
|
function formatBytes(bytes: number): string {
|
|
if (bytes < 1024 * 1024) return `${Math.max(1, Math.round(bytes / 1024))} KB`;
|
|
return `${(bytes / 1024 / 1024).toFixed(bytes < 10 * 1024 * 1024 ? 1 : 0)} MB`;
|
|
}
|
|
|
|
/** Rejects requests whose body is larger than `maxBytes` (Content-Length check). */
|
|
export function rejectOversizedBody(request: Request, maxBytes: number): Response | null {
|
|
const header = request.headers.get("content-length");
|
|
if (!header) return null;
|
|
const length = Number.parseInt(header, 10);
|
|
if (Number.isFinite(length) && length > maxBytes) {
|
|
return Response.json(
|
|
{
|
|
error: translate(requestLocale(request), "server.bodyTooLarge", {
|
|
size: formatBytes(length),
|
|
limit: formatBytes(maxBytes),
|
|
}),
|
|
kind: "too_large",
|
|
},
|
|
{ status: 413 },
|
|
);
|
|
}
|
|
return null;
|
|
}
|
|
|
|
/**
|
|
* Same-origin check for state-changing requests.
|
|
*
|
|
* There is no cookie-based auth here, so CSRF can't steal a session — but a
|
|
* malicious website could still make the user's browser fire requests at a
|
|
* LAN-hosted Freezmo (and burn their rate limit or, in `server` auth mode,
|
|
* their credits). Browsers always send `Origin` on cross-origin POSTs and
|
|
* cannot forge it, so a mismatch is a reliable signal. Requests without an
|
|
* `Origin` (curl, scripts, native apps) are allowed.
|
|
*/
|
|
export function rejectCrossOrigin(request: Request): Response | null {
|
|
const origin = request.headers.get("origin");
|
|
if (!origin) return null;
|
|
|
|
let originHost: string;
|
|
try {
|
|
originHost = new URL(origin).host;
|
|
} catch {
|
|
return Response.json(
|
|
{ error: translate(requestLocale(request), "server.invalidOrigin"), kind: "forbidden" },
|
|
{ status: 403 },
|
|
);
|
|
}
|
|
|
|
const host = request.headers.get("host");
|
|
if (host && originHost === host) return null;
|
|
|
|
// Next dev/prod behind a proxy may rewrite Host; trust x-forwarded-host too.
|
|
const forwardedHost = request.headers.get("x-forwarded-host");
|
|
if (forwardedHost && originHost === forwardedHost) return null;
|
|
|
|
// Allow the loopback pair (localhost vs 127.0.0.1) for convenience.
|
|
const loopback = new Set(["localhost", "127.0.0.1", "[::1]", "0.0.0.0"]);
|
|
const bare = (value: string) => value.replace(/:\d+$/, "");
|
|
if (loopback.has(bare(originHost)) && loopback.has(bare(host ?? ""))) return null;
|
|
|
|
return Response.json(
|
|
{ error: translate(requestLocale(request), "server.crossOrigin"), kind: "forbidden" },
|
|
{ status: 403 },
|
|
);
|
|
}
|
|
|
|
/**
|
|
* API keys are pasted by humans, so clean them before they go into a header:
|
|
* trim, drop control characters/whitespace (header injection), cap the length.
|
|
*/
|
|
export function sanitiseApiKey(value: string | null | undefined): string {
|
|
if (!value) return "";
|
|
return value
|
|
.replace(/[\u0000-\u001F\u007F-\u009F\s]/g, "")
|
|
.slice(0, 512);
|
|
}
|