The urls/filter chain definitions feature is a convenience that allows you to restrict access to a known URL. The definitions can't be queried based on a particular user, i.e. you can't ask "does user x have access to URL y".
If you want to do that, you could come up with your own UrlPermission concept, or use the existing WildcardPermission syntax, e.g. "/some/path:GET". Then you could create a UrlPermissionFilter that performs a check for these permissions based on the request URL. HTH, -- Les Hazlewood CTO, Katasoft | http://www.katasoft.com | 888.391.5282 twitter: @lhazlewood | http://twitter.com/lhazlewood katasoft blog: http://www.katasoft.com/blogs/lhazlewood personal blog: http://leshazlewood.com On Sun, Jan 1, 2012 at 11:14 AM, jeffp <[email protected]> wrote: > You can set this in the filterChain definitions and Shiro will handle it > transparently. > > Referencing the http://shiro.apache.org/spring.html Spring documentation > > <property name="filterChainDefinitions"> > <value> > # some example chain definitions: > /admin/** = authc, roles[admin] > /docs/** = authc, *perms[document:read]* > /** = authc > # more URL-to-FilterChain definitions here > </value> > </property> > > > -- > View this message in context: > http://shiro-user.582556.n2.nabble.com/How-to-check-url-permission-before-jump-to-that-page-tp7099812p7142143.html > Sent from the Shiro User mailing list archive at Nabble.com.
