OptionalcontentType?: stringOptionalhasSession?: booleanWhether the request already carries a session.
A write with no session may establish one, and a lane cannot: its Set-Cookie is minted in
the speculative run, so the client holds a session id the primary lacks (login looks like a
rejected password). Pinning on this covers login, registration and reset without route names.
Optionalpathname?: stringthe front worker's own pathname, already rewritten; absent pins to the primary
OptionalvisitorPath?: stringthe visitor's own path (pathname is /serve after the rewrite)
OptionalwriteForward?: booleanwhether a lane may execute a write and forward it; off pins every POST to the primary
Which lane answers this request.
Only reads on the serving path are spread. A write goes straight to the primary rather than spending a hop to be refused; the failover path is for a request that turns out to mutate.