File APIs for Java Developers
Manipulate DOC, XLS, PPT, PDF and many others from your application.
http://aspose.com/file-tools
Win a copy of Clojure in Action this week in the Clojure forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

security-constraint

 
Art Van Delay
Greenhorn
Posts: 6
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
In web.xml, <security-constraint> would it be correct to say:

* Leave off <http-method> means allow all
* Leave off <auth-constraint> means allow all
* Specifying element means allow one except for an empty element which means allow none.

Thanks in advnace.
 
Adeel Ansari
Ranch Hand
Posts: 2874
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Art Van Delay:
In web.xml, <security-constraint> would it be correct to say:

* Leave off <http-method> means allow all
* Leave off <auth-constraint> means allow all
* Specifying element means allow one except for an empty element which means allow none.


Yes. Not sure about the second part of the third-one, though.

In web.xml, <security-constraint> would it be correct to say:

* Leave off <http-method> means apply to all Http methods
* Leave off <auth-constraint> means allow all
* Specifying element means allow one except for an empty element which means allow none.
 
AmitKumar Jain
Ranch Hand
Posts: 95
  • 0
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I confirmed the last one too from HFSJ...
I'd also like to add:

<auth-constraint>*</auth-constraint> ==> allow all
<auth-constraint></auth-constraint> ==> allow none
 
Don't get me started about those stupid light bulbs.
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic