We use Harness within a restricted environment monitored via proxy.

Currently, to avoid access restrictions, our proxy team needs to create rules based on the URLs and behaviors of the accessed pages. For some behaviors, such as monitoring pipeline logs in real-time, the browser opens a data stream, which is not a behavior normally accepted by our proxy team's security rules.

I would like to suggest that you evaluate the possibility of creating a standard header for responses coming from Harness, indicating the ID of the account returning the data.

This way, we can more securely enable certain types of behavior that are not normally allowed, configuring the proxy to accept responses coming from our accounts.