3 Replies Latest reply on Dec 9, 2010 7:56 PM by salanis

    MWG7:Ruleset usage with HTTP-Header as main criteria.




      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)?


      Many thanks