Pick a focused question that fits your time, stack, and interview goal.
How much time do you have?
Show one-drill sessions you can finish now.
11 results across 1 active filter
Page 1 of 1
Explains contextual sanitization and treats bypass APIs as narrow security-review decisions rather than general encoding helpers.
Keeps server and client output compatible while isolating browser APIs, user state, and post-render integration.
Chooses browser storage by server transport, lifetime, capacity, query needs, sensitivity, synchronization, and offline behavior.
Combines safe bindings, AOT, dependency discipline, CSP, Trusted Types, and reporting without treating one control as a complete defense.
Explains token storage, cookies, XSS, CSRF, and why browser UI never replaces server authorization.
Balances strict script policy with per-request nonces, dynamic rendering, third-party scripts, caching, and operational rollout.
Uses functional interceptors for cross-cutting transport concerns without hiding domain behavior or unsafe retries.
Keeps Next.js 16 Proxy focused on request routing and optimistic checks rather than data access or final authorization.
Separates missing resources, canonical navigation, authorization outcomes, expected failures, and unexpected exceptions.
Layers optimistic routing checks with secure data-layer authorization across components, actions, and handlers.
Uses guards for navigation UX while keeping permissions and data enforcement on the trusted server.