Ensure JSON Content-Type when proxying to SecurityService

Fixkamo-internal
Shipped
April 21, 2026 at 12:48 AM UTC
Author
kamo
Commit
6dfd2ce

Organization creation returned 415 Unsupported Media Type because upstream Spring expects application/json for @RequestBody. Node fetch could omit or default Content-Type for string bodies; forwardToApi now sets it for JSON payloads, and the org POST route forwards the raw body with an explicit JSON Content-Type.

All changes

Like what you see shipping?

Every one of these updates lands in your workspace automatically. Start free and watch it grow week after week.

Start Free ForeverView Pricing