shoney.arickathil
ffd791d05b
- docs/examples/writeonce-serve -> docs/examples/porch (git mv, history kept); `[deps]` key and import are now `porch` / `porch/http` / `porch/router` - name history preserved on the library README, not rewritten into dated records: writeonce-framework -> writeonce-serve (08-25) -> porch (08-26). Stories, specs, plans and the audit reports keep the older name by the repo's own convention; only live docs and every path link were rewritten - left alone deliberately: `internal/serve.wo`, `pub fn serve`, `serve_conn`, `app.serve(...)` — those are functions, not the module name - web-app/wo.toml comment corrected: it claimed hyphens are not identifier characters and named a key this file never used. lexer.ml's `is_ident_cont` DOES accept `-` (an internal dash is part of the identifier, which is why binary minus needs spaces), so a hyphenated key would be legal too - site now teaches the name: package card, the two-deps chapter and the handlers-are-classes chapter say `porch`; site-accept asserted the old /packages/serve route and caught the rename, as a gate should - gates: web-app 46/0, site 21/0, deps-accept 8/0, oop-e2e 116/0, linkcheck 0 broken / 0 anchors; porch typechecks entry-less as kind=library Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
75 lines
No EOL
3 KiB
Text
75 lines
No EOL
3 KiB
Text
-- http/secure.wo — framework v1 slice 2: the security middlewares and the
|
|
-- trusted-proxy parsing helper. Mechanism here, POLICY in the app — the
|
|
-- same split http/auth.wo keeps. The classes satisfy router's Middleware/
|
|
-- After interfaces STRUCTURALLY at the registration site — no import here.
|
|
|
|
-- The response headers every deployment wants and nobody remembers.
|
|
-- HSTS is deliberately absent: TLS terminates at the proxy (the
|
|
-- framework's standing decision), so Strict-Transport-Security belongs
|
|
-- in the proxy config next to the certificates.
|
|
pub class SecurityHeaders {
|
|
fn after(req: Req, mut r: Resp) {
|
|
r.headers["x-content-type-options"] = "nosniff";
|
|
r.headers["x-frame-options"] = "DENY";
|
|
r.headers["referrer-policy"] = "strict-origin-when-cross-origin";
|
|
}
|
|
}
|
|
|
|
-- CORS, both halves in one class: `before` answers the OPTIONS preflight
|
|
-- (204 with the allow set), `after` stamps Access-Control-Allow-Origin on
|
|
-- every response to a request that carried an Origin. Register it twice —
|
|
-- once as Mw, once as Aw — the structural interfaces make one value
|
|
-- satisfy both. allow_origin is the policy knob ("*" or one origin).
|
|
pub class Cors {
|
|
allow_origin: Text
|
|
|
|
fn before(mut req: Req) -> ?Resp {
|
|
if req.method != "OPTIONS" { return nil; }
|
|
let origin = req.headers["origin"];
|
|
if origin == nil { return nil; }
|
|
let want = req.headers["access-control-request-method"];
|
|
if want == nil { return nil; }
|
|
let h: map<Text, Text> = {};
|
|
h["access-control-allow-origin"] = self.allow_origin;
|
|
h["access-control-allow-methods"] = "GET, POST, PUT, DELETE, OPTIONS";
|
|
h["access-control-allow-headers"] = "authorization, content-type";
|
|
h["access-control-max-age"] = "600";
|
|
return Resp { status: 204, headers: h, body: "" };
|
|
}
|
|
|
|
fn after(req: Req, mut r: Resp) {
|
|
let origin = req.headers["origin"];
|
|
if origin != nil {
|
|
r.headers["access-control-allow-origin"] = self.allow_origin;
|
|
}
|
|
}
|
|
}
|
|
|
|
-- Host validation: a request whose Host header is missing or not the
|
|
-- one this app serves answers 421 (misdirected request) before any
|
|
-- route runs. Port suffixes count as part of the host on purpose —
|
|
-- behind the proxy the forwarded Host is exactly one known value.
|
|
pub class HostAllow {
|
|
host: Text
|
|
fn before(mut req: Req) -> ?Resp {
|
|
let got = req.headers["host"];
|
|
if got != nil {
|
|
if trim(got) == self.host { return nil; }
|
|
}
|
|
let h: map<Text, Text> = {};
|
|
h["content-type"] = "application/json";
|
|
return Resp { status: 421, headers: h, body: "{\"error\":\"misdirected request\"}" };
|
|
}
|
|
}
|
|
|
|
-- The PARSING half of trusted-proxy client identity: the left-most
|
|
-- X-Forwarded-For entry, trimmed; "" when absent. VERIFYING that the
|
|
-- peer actually is the trusted proxy needs a peer-address runtime seam —
|
|
-- story 35's, not this slice's.
|
|
pub fn client_ip(req: Req) -> Text {
|
|
let xff = req.headers["x-forwarded-for"];
|
|
if xff == nil { return ""; }
|
|
let parts = split("${xff}", ",");
|
|
if len(parts) == 0 { return ""; }
|
|
return trim(parts[0]);
|
|
} |