Proxy Connection Fix for Agent-Based Scans

Agent connections through an HTTP proxy were previously failing because the agent read configuration keys as proxyHost / proxyPort (lowercase) while the configuration stored them as ProxyHost / ProxyPort (capitalized), resulting in a null host. Both the authenticated and unauthenticated proxy code paths have been corrected to use the right key names. No configuration changes are needed on the customer side.

Where the fix appears

The corrected proxy behavior is visible in the following locations:

Location	What changed
Customer environments using HTTP proxy	Agents successfully connect through the proxy.
Agent logs	No more proxy-initialization failures at startup.

Note: No action is required. Deploy the patched agent build to apply the fix. No configuration changes are needed.