I have a question regarding HTTP-Header as the main criteria for ruleset usage. It works fine for HTTP traffic, but doesn`t work for SSL traffic. We are using a proxy chain, and the first proxy add the HTTP-Header (no ssl termination activated) to the CONNECT command. I think further request will not be transmitted with the Header from first proxy, because of end-to-end encryption.
Question: Is there a way to follow up the session for the mwg appliance without the HTTP-Header attached to further requests, or do we have to use an explicit port for that (without HTTP Header)?
I apologize if I misunderstood your question but what you're saying is the first proxy adds an HTTP header to the CONNECT request and want to know if the Web Gateway as a proxy chain can remove this header and still forward the request?
Or are you asking if there is a way that you can add an HTTP header to your CONNECT request so that you can apply a specific rule/policy for this request?
Hello, I am asking for the second option (add header on first proxy to apply specific rules/policies within SSL connections).