Issuing POST commands via the proxy

When you issue API requests to QRS via the QPS URL, the requests are redirected to a login page before being returned to QRS to perform the specified action. GET commands normally flow through this authentication path without any issues. However, the redirection process can turn POST requests into GET requests, which means that they may fail.

This behavior is not exhibited when connecting directly to the QRS API using a certificate.

To issue POST commands via the proxy, perform a GET request first. The GET request returns sessions cookies that you include in subsequent requests so that they don't have to be re-authenticated. Depending on the tools you use, you may have to extend the simple connection examples to handle cookies between requests.

Did this information help you?

Thanks for letting us know. Is there anything you'd like to tell us about this topic?

Can you tell us why it did not help you and how we can improve it?