title: In PHP is it ok to overwrite $_REQUEST?
body: <blockquote>
    <p><strong>Possible Duplicate:</strong><br>
    <a href="https://stackoverflow.com/questions/2142497/whats-wrong-with-using-request">What&#39;s wrong with using $_REQUEST[]?</a>  </p>
  </blockquote>
  
  
  
  <p>My understanding is the PHP sets up $_REQUEST for both POST and GET request types. While building a restful api I'm using PUT and DELETE as well. Rather than create a new $PUT or $DELETE variable to store this in, is there any valid reason not to use $_REQUEST? I would think using the same mechanism, $_REQUEST, throughout all the code would be better, more readable and more understandable than using 2 or 3 mechanisms depending on request type.</p>
  
  <p>By valid I mean answers like 'bad practice' aren't valid to me... <em>why</em> is it bad practice?</p>
  
  <p>code: <code>parse_str($request-&gt;data, $_REQUEST);</code></p>
  
  <p>I've read <a href="https://stackoverflow.com/questions/6270033/overwriting-post-for-put-or-delete-requests">Overwriting $_POST for PUT or DELETE requests</a> but that would overwrite $_POST with PUT data, that to me would be wrong as $_POST is describing POST data not PUT data in the name of the variable. I also have read the answer there - create a accessor class. But this now leaves 2 mechanisms to access passed user date, the class and $_REQUEST.</p>