Dangerous Code – Case for Java EE
When writing a Java web application is very easy to inadvertently introduce security holes if you are primarily relying on security constraints specified in the web.xml. Security constraints specified in web.xml enforce access by examining the requested URL. This works fine as long as you aren’t programmatically dispatching pages within Java code.Hint: unless the web …
You must be logged in to post a comment.