An unexplained 403 from the bridge now logs which system rejected it and can be retried instead of dropping the connection.
What's wrong with this entry?
A 403 from the bridge endpoint that is not a recognised rejection now derives a source from the response headers, logs it, and attaches it to the terminal rejection result. A nonOrigin403Transient option lets such a 403 be retried rather than ending the connection.
[code-session] /bridge 403 source=
Strings lifted out of the shipped bundle, so the claim above can be checked against them.
Related
Other releases about the same thing. Found by shared names or similar wording; neither means one caused the other.
-
v2.1.222
Bridge recovery has a rebuild budget and richer failure telemetry
Both mention bridge
-
v2.1.224
Two new remote-config gates for bridge event forwarding
Both mention bridge
-
v2.1.234
Remote bridge replaces stale-epoch recovery with a one-shot supersession close
Both mention bridge