boxed wrote:
Sure... but, is this something that should be included in the scope of WW? I guess that's the basic question. WW is a command framework that works great on the web.Why can't you write a filter that reads a config file and checks the incoming URL to see if it is requesting an action that you would like to restrict access to? How does that solution not solve your problem?Seems to me like this is asked for a lot, shouldn't a solution like the one you suggested be included in WebWork?
Is it possible to do such a filter but not tie it too much to WebWork?
/Rickard
-------------------------------------------------------
This SF.net email is sponsored by: ApacheCon, November 18-21 in
Las Vegas (supported by COMDEX), the only Apache event to be
fully supported by the ASF. http://www.apachecon.com
_______________________________________________
Opensymphony-webwork mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/opensymphony-webwork
