title: Is the Content-Type header appropriate for any HTTP verb other than PUT or POST?
body: <p>I'm trying out the REST API of the CollectionSpace software, and noticed that sending it a Content-Type header as part of a GET request results in the following error:</p>
  
  <pre><code>HTTP Status 415 - Cannot consume content type
  </code></pre>
  
  <p>Both of the python REST client libraries I've tried, restclient on github and python-rest-client on google code, do send a Content-Type header when making GET requests.</p>
  
  <p>My understanding from reviewing <a href="http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html" rel="nofollow">http://www.w3.org/Protocols/rfc2616/rfc2616-sec14.html</a> is that clients should only send Content-Type headers on POST and PUT requests. Is that correct? </p>
  
  <p>The fact that both of these libraries do sent the header makes me think that servers typically ignore it, rather than return a client error code.</p>