Skip to content

[IDEA] Use standard configuration options for HTTP Client #117

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
mgaffigan opened this issue Jun 5, 2025 · 0 comments
Open

[IDEA] Use standard configuration options for HTTP Client #117

mgaffigan opened this issue Jun 5, 2025 · 0 comments
Labels
enhancement New feature or request

Comments

@mgaffigan
Copy link
Contributor

Using non-standard HTTP client configuration creates a tripping hazard to anyone new to mirth. Unless I'm mistaken, all functionality already exists in normal java http configuration options.

Current behavior:
Administrators have limited ability to control HTTP Client using standard configuration options. Deployment behind proxies and reverse proxies is also limited by the requirement to use HTTPS, which is inappropriate for many modern deployment and development circumstances. Future SSL "best-practice" requires code changes.

Desired behavior:
By default, respect standard Java options for HTTP Client, and only use non-system-default HTTP options when explicitly configured on a channel with exposed UI.

Considerations:
Keep a secure-by-default posture in the quick-start setup installer.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

1 participant