We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
I am trying to pass certificate (cert.pem and key.key) in the chakram.get using the following options:
var config = { agentOptions : { key: fs.readFileSync(certfilePath), cert: fs.readFileSync(keyfilePath), Passphrase: passPhrase, securityOptions: 'SSL_OP_NO_SSLv3', rejectUnauthorized : false, secureProtocol: 'SSLv3_method' } };
chakram.get(endPoint,queryString,config);
Getting the following error:
when i analysed the Request object inside the Response object, i am not getting the agentOptions .
I am not sure when I am passing the agentOptions in the Get request, still not able to set them.
Does someone else getting this error too while trying to send Certificates in the GET call.
The text was updated successfully, but these errors were encountered:
No branches or pull requests
I am trying to pass certificate (cert.pem and key.key) in the chakram.get using the following options:
var config = {
agentOptions : {
key: fs.readFileSync(certfilePath),
cert: fs.readFileSync(keyfilePath),
Passphrase: passPhrase,
securityOptions: 'SSL_OP_NO_SSLv3',
rejectUnauthorized : false,
secureProtocol: 'SSLv3_method'
}
};
chakram.get(endPoint,queryString,config);
Getting the following error:
<title>400 No required SSL certificate was sent</title>400 Bad Request
No required SSL certificate was sentnginx
when i analysed the Request object inside the Response object, i am not getting the agentOptions .
I am not sure when I am passing the agentOptions in the Get request, still not able to set them.
Does someone else getting this error too while trying to send Certificates in the GET call.
The text was updated successfully, but these errors were encountered: