Some years ago, the w3c documented a proposal for a method called QUERY, where query information may be passed in as the request body rather than on the request line in query parameters. You can see this here: https://www.w3.org/2012/ldp/wiki/Proposal_for_HTTP_QUERY_Verb
I realize you can send any made up verb name along with your HTTP request, however I would like to hear your opinions on the professionalism of adopting a verb like QUERY before that method is accepted as an RFC. If not off-topic, I would welcome exemplary precedents and resources on implementing QUERY.
A Little More Background On QUERY
Just for clarification, my interest in justifying implementing QUERY has 3 primary reasons.
1) Privacy Many HTTP servers, proxies and even application implementations have a tendency to log the entire URI as part of its basic access logs. It is entirely possible that a system may need to be queried by certain attributes that affect regulatory compliance, especially in payment or health systems. Having those query parameters showing up in access logs may be unacceptable.
2) Size Also not mentioned in the w3c proposal is the size constraint of the request line by many HTTP implementations. While not necessarily specified, I have seen issues with some HTTP applications (client & server) failing to handle a request with a certain long length of that request line.
3) Query Complexity Complexity is already well justified in the w3c proposal.