A wildcard redirect from *.scalev.id to *.scalev.com also matched api.scalev.id, causing API requests, including POST requests, to be redirected instead of reaching the API directly.

Impact: Clients calling api.scalev.id received redirect responses for API calls. Some integrations could fail because clients may not follow redirects for POST, or may drop/change the request body during redirect handling.

Root cause: The redirect rule was too broad and did not exclude API hostnames.

Fix: Excluded api.scalev.id from the wildcard redirect and verified that POST requests reach the API without a redirect.