I tried to generate mock server using apidog but I am getting the ssl issue

Get Support
1

I created mock endpoint https://mock.apidog.com/m1/449293-0-default/UdalostiRequest It can be called only if I disable ssl verification in my client. Unfortunatell I cannot tur-off the ssl check in the application from which I am trying to connect to the mock. Also the curt in Windows gives me an error. Am I missing some important config in the apidog mock server so the endpoint is not configured properly? Thank you.

C:>curl --location “http://mock.apidog.com/m1/449293-0-default/UdalostiRequest” --header “Content-Type: application/json” --data “{}”
curl: (35) schannel: next InitializeSecurityContext failed: Unknown error (0x80092012) - The revocation function was unable to check revocation for the certificate.

image.png
image.png1080×145 15.9 KB

2

Please provide the following information:

  • The version of cURL you are using.
  • Your operating system.
  • The output of the following commands:
export | grep -i proxy
curl --version
uname -a
cat /etc/os-release
3

You can also try executing the curl with the -k -vvI option.

4

I am calling it from Windows 10 Professional, so I cannot execute the provided commands since these are for Linux.

C:>curl --version
curl 8.4.0 (Windows) libcurl/8.4.0 Schannel WinIDN
Release-Date: 2023-10-11
Protocols: dict file ftp ftps http https imap imaps pop3 pop3s smtp smtps telnet tftp
Features: AsynchDNS HSTS HTTPS-proxy IDN IPv6 Kerberos Largefile NTLM SPNEGO SSL SSPI threadsafe Unicode UnixSockets

5

C:>curl -k -vvI https://mock.apidog.com/m1/449293-0-default/UdalostiRequest

  • Trying 108.138.7.55:443…
  • Connected to mock.apidog.com (108.138.7.55) port 443
  • schannel: disabled automatic use of client certificate
  • ALPN: curl offers http/1.1
  • ALPN: server accepted http/1.1
  • using HTTP/1.1

HEAD /m1/449293-0-default/UdalostiRequest HTTP/1.1
Host: mock.apidog.com
User-Agent: curl/8.4.0
Accept: /

< HTTP/1.1 404 Not Found
HTTP/1.1 404 Not Found
< Content-Type: application/json; charset=utf-8
Content-Type: application/json; charset=utf-8
< Content-Length: 131
Content-Length: 131
< Connection: keep-alive
Connection: keep-alive
< Date: Wed, 31 Jan 2024 17:15:32 GMT
Date: Wed, 31 Jan 2024 17:15:32 GMT
< x-amzn-RequestId: 60145a03-a81e-41bc-a34b-1e6981b02db4
x-amzn-RequestId: 60145a03-a81e-41bc-a34b-1e6981b02db4
< access-control-allow-origin: *
access-control-allow-origin: *
< x-amzn-Remapped-content-length: 131
x-amzn-Remapped-content-length: 131
< x-amz-apigw-id: Saj4OHn2IAMEC1w=
x-amz-apigw-id: Saj4OHn2IAMEC1w=
< etag: W/“83-TT5yhX0qUUqKhGrxf/P4WhhOOVo”
etag: W/“83-TT5yhX0qUUqKhGrxf/P4WhhOOVo”
< x-powered-by: Express
x-powered-by: Express
< X-Amzn-Trace-Id: Root=1-65ba8034-25aa7ee0213a29b429e84eae;Parent=0d74b8b99447c04c;Sampled=0;lineage=558a2b7c:0
X-Amzn-Trace-Id: Root=1-65ba8034-25aa7ee0213a29b429e84eae;Parent=0d74b8b99447c04c;Sampled=0;lineage=558a2b7c:0
< X-Cache: Error from cloudfront
X-Cache: Error from cloudfront
< Via: 1.1 ecb3ea567a6c6095a23354fbdc938128.cloudfront.net (CloudFront)
Via: 1.1 ecb3ea567a6c6095a23354fbdc938128.cloudfront.net (CloudFront)
< X-Amz-Cf-Pop: FRA56-P6
X-Amz-Cf-Pop: FRA56-P6
< X-Amz-Cf-Id: KcJftr9gU_sT9KpBTy3h7ZN0V7-UC6S57ktFViXQL8dxnj6H4EmP7A==
X-Amz-Cf-Id: KcJftr9gU_sT9KpBTy3h7ZN0V7-UC6S57ktFViXQL8dxnj6H4EmP7A==

<

6

We had replacing it with a more compatible certificate, you can try it out without -k option, and it should be working now.