|
|
Thanks to all who assisted with getting things moving forward cleanly with with OAuth. With your help I was able to get requests with OAuth moving and collectively a number of bugs were fixed.
That said I've discovered the issue that has been preventing the POST operations from working reliably/at all. Currently the entire system utilized SignPost and HTTPUrlConnection. As described on the SignPost website:
NOTE: When using HttpURLConnection, you cannot sign POST requests that carry query parameters in the message payload (i.e. requests of type application/x-www-form-urlencoded). This is not a limitation of Signpost per se, but with the way URLConnection works. Server communication with URLConnection is based on data streams, which means that whenever you write something to the connection, it will be sent to the server immediately. This data is not buffered, and there is simply no way for Signpost to inspect that data and include it in a signature. Hence, when you have to sign requests which contain parameters in their body, you have to use an HTTP library like Apache Commons HttpComponents and the respective Signpost module. (This restriction does not apply to requests which send binary data such as documents or files, because that data won't become part of the signature anyway.)
|
Locked
