2 Replies Latest reply: Jan 31, 2013 1:42 AM by mgarten RSS

    Usage of via string from Header

    mgarten

      Dear All,

       

      since long time we are using the via string from the header within a rule to make a  decision within a rule.

      It was implemented with version 7.1.6

       

      Now we started to use 7.3.0.2.0.

      And now we can't use more the via string.

       

      Here an example how we have implemented it in a rule:

      Header.Request.Get("via") matches *111.111.111.111*

       

      Also if we try to show the via string in a block message now the value is empty.

       

      Does somebody have a solution for this?

       

      Thanks

       

      mgarten

        • 1. Re: Usage of via string from Header
          eelsasser

          I do not see that behaviour on my 7.3.0.2.

          I have a rule that blocks on this criteria:

            Header.Request.Get ("Via") matches *192.168.2.232*

           

          And when i forward from another proxy with that IP address, it blocks as it should.

           

          This rule is at the top in only the request cycle, then i have another rule below that in the request/response cycle that removes the Via header as it goes out to the internet.

           

          i don't know why it wouldn't work for you.

          • 2. Re: Usage of via string from Header
            mgarten

            Hello,

             

            thanks for the answer.

            To specify this here some more information.

            I can see the via information for a normal request but I can't see the via information in context with "next hop proxy".

            So I have open a case at McAfee. Let see what they can find out.

            Thanks

             

            mgarten