title: Querystring in REST Resource url
body: <p>I had a discussion with a colleague today around using query strings in REST URLs. Take these 2 examples:</p>
  
  <pre><code>1. http://localhost/findbyproductcode/4xxheua
  2. http://localhost/findbyproductcode?productcode=4xxheua
  </code></pre>
  
  <p>My stance was the URLs should be designed as in example 1. This is cleaner and what I think is correct within REST. In my eyes you would be completely correct to return a 404 error from example 1 if the product code did not exist whereas with example 2 returning a 404 would be wrong as the page should exist. His stance was it didn't really matter and that they both do the same thing.</p>
  
  <p>As neither of us were able to find concrete evidence (admittedly my search was not extensive) I would like to know other people's opinions on this.</p>