Currently, context forge gateway defaults to sending requests with:
Content-Type: application/json
This makes it difficult to integrate with APIs or services that require:
Content-Type: application/x-www-form-urlencoded

Suggested Solution(s)
Provide an option (e.g., config, request parameter) that allows requests to use application/x-www-form-urlencoded instead of being locked to JSON.
Allow Content-Type override via configuration.

Automatically encode the body properly when application/x-www-form-urlencoded is selected.