Topic
  • 4 replies
  • Latest Post - ‏2013-06-29T01:00:37Z by Rohit-Goyal
thotranh
thotranh
109 Posts

Pinned topic NOT matching rule

‏2013-06-27T15:59:57Z |

Please help .

How do we define a NOT matching rule ?

For example : I want to matching all URLs except the one that ends with *.css

Thank you

  • HermannSW
    HermannSW
    6206 Posts

    Re: NOT matching rule

    ‏2013-06-28T09:48:32Z  

    A general answer on this is difficult.

    But just answering your sample, have two rules:

    1. matching the ones that end with .css
    2. match all

    That way the 2nd rule gets only matched for the cases you want,

    You have to do in 1st rule what you want to happen for the .css case, eg. raise and error.


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/>

  • thotranh
    thotranh
    109 Posts

    Re: NOT matching rule

    ‏2013-06-28T13:07:01Z  
    • HermannSW
    • ‏2013-06-28T09:48:32Z

    A general answer on this is difficult.

    But just answering your sample, have two rules:

    1. matching the ones that end with .css
    2. match all

    That way the 2nd rule gets only matched for the cases you want,

    You have to do in 1st rule what you want to happen for the .css case, eg. raise and error.


    Hermann<myXsltBlog/> <myXsltTweets/> <myCE/>

    Thank you .

    I am still not able to implement my scenario.

    This is my simple policy :

    Matching Rule ---  AAA --- Result.

    When a request comes in , I don't want URL that ends with .css to go through AAA (ie bypassing AAA).  For any other request, go through AAA.

    Right now, the matching rule is just "match-any-url", so everything has to be authenticated , but I don't want the requests for "css" to be authenticated ...

    Please be more specific for what I need to do to the matching rule if possible. Greatly appreciate your help !

     

  • swlinn
    swlinn
    1395 Posts

    Re: NOT matching rule

    ‏2013-06-28T15:49:35Z  
    • thotranh
    • ‏2013-06-28T13:07:01Z

    Thank you .

    I am still not able to implement my scenario.

    This is my simple policy :

    Matching Rule ---  AAA --- Result.

    When a request comes in , I don't want URL that ends with .css to go through AAA (ie bypassing AAA).  For any other request, go through AAA.

    Right now, the matching rule is just "match-any-url", so everything has to be authenticated , but I don't want the requests for "css" to be authenticated ...

    Please be more specific for what I need to do to the matching rule if possible. Greatly appreciate your help !

     

    I don't believe the matching rule can do this for you.  What I would do is use a transformation stylesheet that inspects var://service/URI and outputs a nodeset that can be used by a conditional action which will conditionally drive the AAA action.

    Regards,

    Steve

  • Rohit-Goyal
    Rohit-Goyal
    151 Posts

    Re: NOT matching rule

    ‏2013-06-29T01:00:37Z  
    • thotranh
    • ‏2013-06-28T13:07:01Z

    Thank you .

    I am still not able to implement my scenario.

    This is my simple policy :

    Matching Rule ---  AAA --- Result.

    When a request comes in , I don't want URL that ends with .css to go through AAA (ie bypassing AAA).  For any other request, go through AAA.

    Right now, the matching rule is just "match-any-url", so everything has to be authenticated , but I don't want the requests for "css" to be authenticated ...

    Please be more specific for what I need to do to the matching rule if possible. Greatly appreciate your help !

     

    This is what you can try

    1) Match (*.css) -> Result

    2) Match (*) -> AAA -> Result

    Remember to maintain the order as I mentioned above.

    This way *.css requests will pass without AAA.

    Rohit