What are practical use-cases for the HTTP verb REPORT and why is it neglected over time? : <p>Whenever I have to create a RESTful web service and the use case implies on getting data based on a set of search criteria, I always opted for a POST request with the parameters in the body instead of a GET request for all the obvious reasons. I've seen it a dozen of times so I figured is was best practice.</p>

<p>Most recently I stumbled upon <a href="https://evertpot.com/dropbox-post-api" rel="noreferrer">this interesting blog article by Evert Pot</a> where he comments on the downsides of the POST verb and simply notes on using the <strong>REPORT</strong> verb instead. He also states that <em>"its semantics are well defined and it works everywhere"</em>. 
After reading the post I've been trying to find some more information on this REPORT verb but not much can be found. I know it was part of <a href="https://tools.ietf.org/html/rfc3253#section-3.6" rel="noreferrer">RFC-3253</a> as a way to obtain information about a resource but other than that I am clueless.</p>

<p>My question are the following:</p>

<ol>
<li>Is REPORT really a better alternative than POST in the case of requesting a resource based on a set of search criteria?</li>
<li>Is it wise to start using it or is it too risky? I'm seeing lots of 
<code>HTTP Method REPORT not supported</code> issues from various tools and frameworks.</li>
<li>Why does it seem like it is neglected over the years and why do we
know so little about it?</li>
<li>What could other valid use-cases be for using this verb?</li>
</ol>

<p>Thank you in advance.</p>
