Results 1 to 3 of 3

Thread: Intercept-url pattern

  1. #1

    Default Intercept-url pattern

    Hi Guys,

    I would like to ask the following question but this is not stopped just want to know any other way to configure this setting.

    As we know the intercept-url pattern will check the ROLE_** from accessing the url

    Example:

    <intercept-url pattern="/car/**" access="ROLE_ADMIN" />
    When the user have the ROLE_ADMIN he/she can access whatever method under /car, correct me if I wrong

    And now I want to configure under car any get** method can be access by ROLE_USER however after I configure the following ROLE_ADMIN user unable to access any get**

    <intercept-url pattern="/car/get**" access="ROLE_USER" />
    If the get** method can be access by ROLE_ADMIN so I need manual configure as below

    <intercept-url pattern="/car/get**" access="ROLE_USER, ROLE_ADMIN" />
    Is this the normal behavior? As the /car/** already define ROLE_ADMIN can access whatever method under the car

    Thank You

    - David

  2. #2
    Join Date
    Jun 2006
    Location
    The Netherlands
    Posts
    13,625

    Default

    That is the intended and expected behavior...
    Marten Deinum
    Java Consultant / Pragmatist / Open Source Enthousiast / Author


    Pro Spring MVC: With Web Flow
    Conspect

    Have you read the reference guide.
    Use the [ code ] tags, young padawan

  3. #3

    Default

    OK and noted. Thank you for the reply

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •