{"version":"2.1.238","anchor":"bridge-403s-log-which-system-rejected-them","canonical_anchor":"bridge-403s-log-which-system-rejected-them","heading":"Bridge 403s log which system rejected them","tier":"internal","area":"Remote Bridge","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238\/e\/bridge-403s-log-which-system-rejected-them","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.238","markdown":"### Bridge 403s log which system rejected them\n\nAn unexplained 403 from the bridge now logs which system rejected it and can be retried instead of dropping the connection.\n\n**What**\n\nA 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.\n\n**Evidence**\n\n`[code-session] \/bridge 403 source=`\n\n- Area: Remote Bridge\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}