This commit corrects the placement of the `disable_referer_header`
configuration option. It is now correctly part of the `reverse_proxy`
settings, as intended, rather than the general `proxy` settings.
When `reverse_proxy.disable_referer_header` is set to `true`,
tuliprox will not send the Referer header in its outgoing HTTP
requests made as part of its reverse proxy functionality.
This is useful for scenarios where Xtream Codes providers or other
services are restrictive and might block requests that include
the Referer header, especially after redirects.
The following changes were made:
- Removed `disable_referer_header` from `ProxyConfig` in `src/model/config_proxy.rs`.
- Added `disable_referer_header: bool` to `ReverseProxyConfig` in `src/model/config.rs`.
- Updated client creation in `src/api/main_api.rs` (within `create_shared_data`)
to honor this flag from `ReverseProxyConfig`.
- Removed referer disabling logic from the general `create_client` function
in `src/utils/network/request.rs`.
- Updated `config/config.yml` to move the option to the `reverse_proxy` section.
- Updated `README.md` to reflect the correct placement and usage.
google-labs-jules[bot]