import { readFileSync } from "node:fs"; import { expect, test, type Page } from "../support/browser/strict-browser-test.ts"; // 13-08. The Content-Security-Policy in config/hosting/security-headers.json was // declared but never applied in a browser: `vite preview` sends no security // headers. This smoke serves the build with the production headers attached // and fails on any securitypolicyviolation event or console error. const { headers: declaredHeaders } = JSON.parse( readFileSync("config/hosting/security-headers.json", "utf8"), ) as { headers: Record }; // The preview server is plain HTTP on loopback. `upgrade-insecure-requests` is a // no-op for an HTTPS origin, but WebKit applies it to loopback and rewrites // every same-origin request to https, which this server cannot answer. Every // other directive is served exactly as declared. const securityHeaders = { ...declaredHeaders, "Content-Security-Policy": declaredHeaders["Content-Security-Policy"]! .split(";") .map((directive) => directive.trim()) .filter((directive) => directive !== "upgrade-insecure-requests") .join("; "), }; // F-7. No zod setup here: the app sets `jitless` in src/contracts/zod.ts before // any schema is built, so zod's `Function("")` probe never reaches the policy. test.beforeEach(async ({ page, baseURL }) => { const origin = new URL(baseURL ?? "http://127.0.0.1:4173").origin; await page.route( (url) => url.origin === origin, async (route) => { const response = await route.fetch(); await route.fulfill({ response, headers: { ...response.headers(), ...securityHeaders }, }); }, ); await page.addInitScript(() => { const violations: string[] = []; Object.defineProperty(window, "__cspViolations", { value: violations }); document.addEventListener("securitypolicyviolation", (event) => { violations.push(`${event.effectiveDirective} ${event.blockedURI}`); }); }); }); async function cspViolations(page: Page): Promise { return page.evaluate(() => (window as unknown as { __cspViolations: string[] }).__cspViolations); } test("boots and changes route under the production security headers", async ({ page }) => { const response = await page.goto("/"); expect(response?.headers()["content-security-policy"]).toBe( securityHeaders["Content-Security-Policy"], ); // Template sync (af3d8e6): TechLog's home and a primary-navigation page in // place of upstream's example screens. await expect(page.getByRole("heading", { level: 1 })).toHaveText("TechLog"); await page .getByRole("navigation", { name: "주요 탐색" }) .getByRole("link", { name: "프로젝트" }) .click(); // Upstream also waits for route focus here. TechLog's Public shell does not // move focus on navigation (app-router.tsx leaves it to the shell); that is // app-shell.spec.ts's to check, so this smoke stays about the policy. await expect(page).toHaveURL(/\/projects$/); await expect( page.getByRole("heading", { level: 1, name: "프로젝트" }), ).toBeVisible(); expect(await cspViolations(page)).toEqual([]); });