topic Re: HTTP Request: Post error: InitializeSecurityContext failed: The revocation function was unable t in Discussions

HTTP Request: Post error: InitializeSecurityContext failed: The revocation function was unable to ch

bayesfactor — Wed, 20 Feb 2019 22:57:48 GMT

I have an error creating a post request, the error returned is:

New HTTP Request()
POST [url]
schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

The solutions here didn't work for me, I got the same error message as .

My code is approximately:

request = HTTPRequest(
  Url(url),
  Method("POST"),
  Headers( {"Accept: application/json"}, {"Authorization = Bearer " }),
  JSON(json)
);

Why isn't jsl on stackoverflow?

Re: HTTP Request: Post error: InitializeSecurityContext failed: The revocation function was unable t

bryan_boone — Wed, 20 Feb 2019 22:36:25 GMT

I'm not sure if you left the Authorization token off of your header.
You have
"Authorization = Bearer"
Usually it's
"Authorization: Bearer [and some authorization key]"

If you do have it correct and there's a problem with the server side security ticket, you can use
request << Insecure (1)
which works like:

From curl's manpage

-k, --insecure (SSL) This option explicitly allows curl to perform "insecure" SSL connections and transfers. All SSL connections are attempted to be made secure by using the CA certificate bundle installed by default. This makes all connections considered "insecure" fail unless -k, --insecure is used.

Re: HTTP Request: Post error: InitializeSecurityContext failed: The revocation function was unable to ch

bryan_boone — Mon, 25 Nov 2019 22:37:25 GMT

You can use the Insecure option.

request = HTTPRequest(
  Url(url),
  Method("POST"),
  Headers( {"Accept: application/json"}, {"Authorization = Bearer " }),
  JSON(json),
  Insecure(1)
);

It won't verify the certificate just like:

k, --insecure (SSL) This option explicitly allows curl to perform "insecure" SSL connections and transfers. All SSL connections are attempted to be made secure by using the CA certificate bundle installed by default. This makes all connections considered "insecure" fail unless -k, --insecure is used.