| instrumented-redirect-handler wraps the existing redirect-handler with registration + state tracking | |
. register-request! stashes :cyclops-request-id on the worker's property list BEFORE storing the registry entry, so the reaper (which keys on the property list) can never observe an entry whose worker doesn't yet claim it. After this filter returns, the request continues into either aserve's proxy-request (when a rule matched) or another locator/entity. The reaper removes the registry entry once the worker takes its NEXT request — but for the non-proxy path we finalize immediately because the worker may sit idle for a long time before rolling over. | |