KamoCRM

Resolve org/member context from *** session for billing proxy

Fixkamo-internal
Ya
17 Aprili 2026, 03:13 UTC
Mwandishi
kamo
Ahadi ya
936da4a

BillingService controllers require X-Org-Id and X-Member-Id headers. When calling directly (bypassing APIService), these weren't being set. Now the Next.js proxy reads the *** cookie, looks up the session in Redis, extracts orgID and memberID, and forwards them as headers.

Mabadiliko yote

Je, unaona nini kuhusu usafiri?

Kila kitu kinaingia kwenye tovuti yako mwenyewe. Anza kwenye mpango wa bure na usome ukurasa huu tena katika mwezi mmoja.

Kuwa Huru MileleMtazamo wa bei