Skip to content
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

More flexible Proxy configuration in API-Firewall #97

Closed
0x566164696D opened this issue May 22, 2024 · 1 comment
Closed

More flexible Proxy configuration in API-Firewall #97

0x566164696D opened this issue May 22, 2024 · 1 comment

Comments

@0x566164696D
Copy link

Currently, proxying is configured only through --server-url.
If --server-url contains a DNS name, it is resolved to an IP, a connection is established with this IP, and the DNS name is written to header_host.
If an IP address is specified, the connection is made to it, and it is also placed in the header_host of the HTTP request.

This approach is not flexible enough.
Please add an additional launch key where an arbitrary header_host can be specified.
This will significantly simplify the integration of API-Firewall into the infrastructure.

@afr1ka
Copy link
Collaborator

afr1ka commented Jun 6, 2024

Added the APIFW_SERVER_REQUEST_HOST_HEADER env variable to set the custom host value for proxied requests in APIFW v0.7.3.

@afr1ka afr1ka closed this as completed Jun 6, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants