mrsarm / reqclient Goto Github PK

Some times (optional parametter?) would be better to get the full response instead of just the body.

A good implementation could be like this: https://github.com/request/request-promise#get-the-full-response-instead-of-just-the-body

I need help to get my access_token. it had been a week but still could't find out how, and decide to request help from here.
I am trying to request post to oauth.opskins but it doesn't see my parametes. How can I send required parameters to server?

var client = new RequestClient({
            baseUrl:"https://oauth.opskins.com/v1/",
            debugRequest:true, debugResponse:true,
            auth:{
                user: '**my_client_id_here**',
                pass: '**my_secret_here**'
            }
        });
    
        var resp = client.post("access_token", {"grant_type": "authorization_code", "code":`${req.query.code}`},{headers: {"authorization":"Basic **my_key-here**"}});

I am getting this output

[Response access_token]<- Status 400 - {"error":"invalid_request","error_description":"The grant_type parameter is required"}

When the request is a file upload take more time than a common request. It will be useful to add one more option to the constructor config with this. Could be timeoutUpload ?

cURL debug output should works in a Bash console, but if the string contains a body with single quote ' character, is misinterpreted by the shell as a end of the body string.

Check this to see how to escape single quote, and check if there is another character that must be escaped.

When a connection with the OAuth fails for example given bad credentials, the connection is rejected with a promise (that's fine), but the content of the promise has an string representation of the error instead of a JSON object. For example a request like this:

[Requesting token]-> -X POST https://api.somesite.com/oauth/token -u ${CLIENT_ID}:${CLIENT_SECRET} -d 'grant_type=client_credentials'
[Response   token]<- Status 401 - {"timestamp":1478781997822,"status":401,"error":"Unauthorized","message":"Bad credentials","path":"/oauth/token"}

In the catch handler:

client.get(...)
.then(function(response) {
  // Things work ...
})
.catch(function(err) {
  console.log("type of err: " + typeof(err)); //--> This print "type of err: string"
});

This request:

client.get({uri:"users", query: {"deleted":false,"status":["new","confirmed"]}})

Will generate this URI:

/users?deleted=false&status=new,confirmed

But must generate:

/users?deleted=false&status=new&status=confirmed

Also a way to overwrite this behavior without overwrite the all _parseUri(uri,options) method would be convenient.

Hello,
I have following code:
var RequestClient = require("reqclient").RequestClient;
var client = new RequestClient({
baseUrl:"http://19.160.168.50:3000/api",
debugRequest:false, debugResponse:true
});
var jsData = { "$class": "org.acme.test.User",
"user_id": "u6","user_oro_id": "rag",
"firstname": "raghav","lastname": "bhatta",
"email": "[email protected]", "Phone": "123",
"address": "adasd", "address1": "asda",
"city":"ada", "state": "asd", "country": "dfd",
"user_type": "dfd"
};
let resp = client.post("User", jsData, {headers: {"Content-Type":"application/json", "Accept":"application/json"}});
But I cannot tapped response. I want to read statusCode from the response which is not happening. Can you please suggest.

Thank you

Currently there is a L1 cache that allows recover the resource from the cache, but if the time expires, reqclient goes to the server to get a fresh value blocking the request until the response (but asynchronous, of course ;) .

The L2 cache could never expire, or have a higher TTL, and the most important, it will allow to reqclient return a value and fire the request to get a fresh value for the next call (the value obtained from the server will update both caches).

The library should use encodeURIComponent() standard method instead of do string replacements manually.

• See gzip and forever param from request module.
• Check performance gained.
• Check forever flag to not block subsequent requests.
• Look at https://stackoverflow.com/questions/28229044/http-keep-alive-in-node-js and https://stackoverflow.com/questions/19043355/how-to-use-request-js-node-js-module-pools