title: CheckMarx XSRF attack issue
body: <p>I have a REST controller, which has a method <code>deleteStudent</code> which accepts two parameters 
  <code>studentId</code> which is <code>Long</code> and <code>section</code> which is <code>String</code>.</p>
  
  <pre><code>@RequestMapping(value="/rest/deleteStudent/studentId/{studentId}/section/{section}", method = RequestMethod.DELETE)
  public  Student deleteStudent(@PathVariable Long studentId, @PathVariable String section){
      return studentService.deleteStudent(studentId ,section);
  }
  </code></pre>
  
  <p>For above code checkmarx is complaining <em>This parameter value flows through the code and is eventually used to modify database contents. 
  The application does not require renewed user authentication for the request. This may enable Cross-Site Request Forgery (XSRF).</em> </p>
  
  <p>I have tried   <code>Htmlutils.htmlescape</code> ( from spring web util) on section but no luck.</p>
  
  <p>How to get rid of this checkmarx issue?</p>
  
  <p>One more thing how  XSRF   and SQL injection attack is possible  if field is  of Long type ?</p>