Problem: the hexagonal refactor churns the backend tree for nine more phases; the UI delivery stack (web/ SPA, cmd/desktop Wails wrapper, compose/web image) must move to its own repo first so doc/layout rewrites land once on a backend-only tree. Change: - New repo git.hubris.network/dtoro/oikos-web (v0.33.0): web/, desktop/ (updateURL repointed to oikos-web releases), compose/, own CI (web + desktop jobs), own deploy script (CI-green gate, TOCTOU guard, version-tagged images, prune-to-3), own webhook receiver on :9798 + launchd unit, own compose project publishing the same 8091:80. - Cutover executed on mac-mini in order: oikos stack's web service stopped+removed, oikos-web project brought up on 8091; outer Caddy untouched (targets the published port) — serving + Authentik flow + /wails 404 quirk verified post-cutover. - Stripped from oikos: web/, cmd/desktop/, compose/web/, desktop CI workflow, ci.yml web job, Makefile ui/desktop/desktop-package/install targets, the compose web service, oikos-web from deploy.sh's fallback prune list; wails + go-keyring dropped from go.mod, vendor synced. - README / CONTRIBUTING / AGENTS.md / .agents dev+operations docs now point at the new repo; mbse + mascot design docs carry a path note. Risk: production SPA serving depends on the new pipeline now; rollback is versioned-image re-up of the old web service from a pre-split checkout (port 8091). Desktop builds installed before the split still check dtoro/oikos releases — one manual reinstall, noted in the oikos-web release notes. Verification: go vet, make test (race), make generate-check, golangci (no new findings; baseline down 400→365); post-cutover curls — localhost:8091 200, /wails/runtime.js 404, outer Caddy 302 Authentik.
41 lines
1.7 KiB
JavaScript
41 lines
1.7 KiB
JavaScript
"use strict";
|
|
Object.defineProperty(exports, "__esModule", { value: true });
|
|
exports.pathMatch = pathMatch;
|
|
/**
|
|
* Answers "does the request-path path-match a given cookie-path?" as per {@link https://www.rfc-editor.org/rfc/rfc6265.html#section-5.1.4 | RFC6265 Section 5.1.4}.
|
|
* This is essentially a prefix-match where cookiePath is a prefix of reqPath.
|
|
*
|
|
* @remarks
|
|
* A request-path path-matches a given cookie-path if at least one of
|
|
* the following conditions holds:
|
|
*
|
|
* - The cookie-path and the request-path are identical.
|
|
* - The cookie-path is a prefix of the request-path, and the last character of the cookie-path is %x2F ("/").
|
|
* - The cookie-path is a prefix of the request-path, and the first character of the request-path that is not included in the cookie-path is a %x2F ("/") character.
|
|
*
|
|
* @param reqPath - the path of the request
|
|
* @param cookiePath - the path of the cookie
|
|
* @public
|
|
*/
|
|
function pathMatch(reqPath, cookiePath) {
|
|
// "o The cookie-path and the request-path are identical."
|
|
if (cookiePath === reqPath) {
|
|
return true;
|
|
}
|
|
const idx = reqPath.indexOf(cookiePath);
|
|
if (idx === 0) {
|
|
// "o The cookie-path is a prefix of the request-path, and the last
|
|
// character of the cookie-path is %x2F ("/")."
|
|
if (cookiePath[cookiePath.length - 1] === '/') {
|
|
return true;
|
|
}
|
|
// " o The cookie-path is a prefix of the request-path, and the first
|
|
// character of the request-path that is not included in the cookie- path
|
|
// is a %x2F ("/") character."
|
|
if (reqPath.startsWith(cookiePath) && reqPath[cookiePath.length] === '/') {
|
|
return true;
|
|
}
|
|
}
|
|
return false;
|
|
}
|