Results 1 to 3 of 3

Thread: Speciying querystring parameter in intercept URL

  1. #1
    Join Date
    Dec 2006
    Posts
    24

    Default Speciying querystring parameter in intercept URL

    Hi,

    I use a MultiActionController with the resolver as ParameterMethodNameResolver. One of the methods needn't be authenticated, so I figured I could specify the URL and give filter=none.

    So I gave this:
    Code:
    <intercept-url pattern="/server/booking" access="IS_AUTHENTICATED_FULLY" />
    <intercept-url pattern="/server/booking?action=init"  filters="none"/>
    But when I turned on debugging, the match was done as follows:
    Request URL "/server/booking" does not match "/server/booking?action=init"

    Why does the request URL strip the querystring parameters being passed to it? Why does it take only till booking?

    help appreciated. thx.

  2. #2
    Luke Taylor is offline Senior Member Acegi Security System TeamSpring Team
    Join Date
    Aug 2004
    Location
    Glasgow, Scotland
    Posts
    3,449

    Default

    The standard ant matching is only intended for simple wildcarded patterns. If you want to match things like query strings or more complicated patterns, then you should change to using regular expressions (use the "path-type" attribute on the <http> element).
    Spring - by Pivotal
    twitter @tekul

  3. #3
    Join Date
    Dec 2006
    Posts
    24

    Default

    Thx mate. That was helpful.

Posting Permissions

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