boxed wrote:

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?

There is a Jira task to make it possible to lock an alias to an absolute path. This is within the scope of WebWork.

There will not be a security framework included with WebWork. It has already been beaten into the ground that there are already many ways to do security. If you're unfamiliar with the debate, go back through the email archives.
WebWork is a component of an webapp solution. Not the whole ball of wax. If the whole world begged for a persistence framework they would get the same lukewarm response.

Sheesh, guys. Half of you are saying WebWork is too hard to learn. The other half is saying let's put in features so that WebWork functions how I want it too, and to hell with the others are going to have to learn to cope with it.

-Maurice

// Anders Hovmöller



-------------------------------------------------------
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




-------------------------------------------------------
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

Reply via email to