Static ReadonlyPREFIX_Static ReadonlyTLS_Staticinthe request
the response
whether the request was marked
StaticisWhether a request was relayed here by another cell, whose front process
translated its Cookie header already. stsCellRelay is set by
common/cell_channel.ts's serveRelayed() on the request object, after
the peer cell's certificate was checked; no header can set it.
the request
true for a relayed request
StaticmiddlewareThe middleware. In a worker it translates only what the front process marked (inWorker()).
an express middleware
StaticprefixStaticserviceEvery name this service's cookies can carry, inside and on the wire, as
prefixes ending in * (2026-11-14). The remote PEP's reverse proxy is
handed them on its pull and never forwards one upstream: a browser sends
cookies by host, not port, so where the service and the proxy share a
host the sign-on session's cookie reached the application. Derived from
the two patterns above, so a cookie added tomorrow is covered.
the prefixes
StaticunwrapPuts a Cookie header into the names the service reads.
the header as the browser sent it
whether __Secure- is a form this service writes
the header with inside names, without what must not be believed
StaticunwrapPuts a request's Cookie header into the inside names, in place, where
the realm's mode prefixes them.
the request
whether the realm's mode prefixes cookies
StaticwireThe name a browser will know a cookie by, for a document that must name it (DBSC's session instructions). Asked in a worker, so it asks the settings.
the inside name
the cookie's attributes
the wire name
StaticwrapPuts one Set-Cookie line into its wire form.
the line as the service wrote it
the line the browser receives
The worker's half: a request the front process marked with TLS_HEADER is translated here, by this process's view of the realm's mode, and the answer tells the front on PREFIX_HEADER whether to prefix its cookies. Anything else is left alone. A method of its own so that a test can drive it from the main thread.