You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@struts.apache.org by Ro...@hydro.qc.ca on 2002/11/01 17:10:09 UTC
RE : url problem when 2 mapping redirect to struts
Ok, my mistake, I missed the warnings when I RTFM.
Now, any ideas on how to put container security on some action without
specifying them all. I don't want to put a pattern like securXXXXX.do
everywhere I need security. I know there is the struts-config action
attribute «roles» but I really prefer a container managed security plus my
exploitation group requires it.
Thank you
Stephan
-----Message d'origine-----
De : Eddie Bush [mailto:ekbush@swbell.net]
Envoyé : vendredi 1 novembre 2002 11:38
À : Struts Users Mailing List
Objet : Re: url problem when 2 mapping redirect to struts
*See...
4.7.2 Configure the Action Servlet Mapping
at ...
*
http://jakarta.apache.org/struts/userGuide/building_controller.html#config
... sometimes it pays to RTFM :-)
Roy.Stephan@hydro.qc.ca wrote:
>I have a container security constraints for all my actions (*.do ).
>
>Now I have the first 3 or 4 actions that do not require authentication. I
>added another servlet mapping entry *.go to redirect to the struts
>controller.
>
>Now all forms submitted. Even if they have an action with the *.do, submit
a
>request with a *.go.
>
>How come the extension of my url is changed?
>
>Thank you.
>Stephan
>
>
>
--
Eddie Bush
--
To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
For additional commands, e-mail:
<ma...@jakarta.apache.org>
Re: RE : url problem when 2 mapping redirect to struts
Posted by Eddie Bush <ek...@swbell.net>.
Well ... you use URL mappings to specify them, right? If you can't
change the ending perhaps you should change something else? ... say:
instead of: *.do
use: /secure/*
... or something along those lines. If I understand right, you probably
won't like that solution. Sorry! You can add multiple constraints, so,
what you might do is just maybe ... specify something like:
/<module>/secure/*
... for each module. You then have a secure area inside of every
module. Now, so far as actually implementing this in your configuration
goes, the path of the action does not have to have anything whatsoever
to do with the physical on-disk structure of your files. Because of
this, you can *easily* specify an action with
'path="/secure/someAction"' - and *boom* it's "secure". That makes it
really easy to make something secure down the road too - just change the
path of the action and restart (and, if Ted gets his "reference actions
by name" proposal in for 1.1 final, you'll be able to [assuming you use
the action name for linking!] rest assured there is nothing else to change!)
You could also have ... say a /pub area vs a /private or /secure or
/<whateveryouwant> area. Again, you have several options.
Roy.Stephan@hydro.qc.ca wrote:
>Ok, my mistake, I missed the warnings when I RTFM.
>Now, any ideas on how to put container security on some action without
>specifying them all. I don't want to put a pattern like securXXXXX.do
>everywhere I need security. I know there is the struts-config action
>attribute «roles» but I really prefer a container managed security plus my
>exploitation group requires it.
>
>Thank you
>Stephan
>
--
Eddie Bush
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>