Learning term
Sticky session — Reverse proxies and routing
Sticky session binds repeated client requests to the same backend instance. This card shows its role in “Reverse proxies and routing” and a safe diagnostic path.
Orientation
Sticky session binds repeated client requests to the same backend instance. At this level, separate purpose, input, and visible result. Place Sticky session within Reverse proxies and routing before changing settings or files.
Practical use
Check the affinity cookie when session-bound state jumps between replicas. Start in a sandbox with neutral examples. Record the expected state, make one controlled change, and compare status output, application behavior, and logs.
Technical understanding
Sticky session binds repeated client requests to the same backend instance. Technically, Sticky session connects through interfaces, configuration, state, or dependencies. Trace data from input to output and check versions, permissions, networking, storage, and resources separately.
Operations and debugging
Check the affinity cookie when session-bound state jumps between replicas. In production-like operations, use measurable signals, least privilege, reproducible configuration, and a documented rollback. Preserve evidence, isolate the cause, and verify the correction with the same test.
Exercise
Try it safely
Check the affinity cookie when session-bound state jumps between replicas. Open an isolated test environment and run “curl -I -H "Host: app.example.com" http://127.0.0.1”. Write down the expected output first, do not alter production data, and record one safe next diagnostic step.
curl -I -H "Host: app.example.com" http://127.0.0.1Quick check
Can you explain the purpose, observable state, and most common failure source of Sticky session — Reverse proxies and routing in one sentence each? Which evidence would you preserve before changing anything, and which repeated test would prove that the correction actually worked?