Please review the information about HTTP headers in Chapter 17.1 of the BPM Suite and BRMS Development Guide (after the unnumbered heading "HTTP Headers in REST API calls") in the context of BXMSDOC-594 and the issues linked therein.

Notes:

• I have not actually found the q parameter to be required in the HTTP 1.1 RFC, therefore I have suggested—but not mandated—its use.
• I am not entirely sure if the list of the allowed content types is exhaustive, but based on the rest of the documentation, I believe it is.