Thank you again.

We continued troubleshooting today.

And by checking logs on server site, we learned that server is sending back a 400. This is why the string of 200 will never be hit in the configured receive string. When drafting the Send string, we following the recommendation in  K2167:

Example send string

GET /index.html HTTP/1.1\r\nHost: host.example.com

Customized it:

GET //api/v1/system/services/status?service_names=nae-kmip HTTP/1.1 \r\nConnection: Close

But server still sends 400.

Interestingly, when using openssl by using the same link we receive HTTPP code 200:

(echo -e "GET /api/v1/system/services/status?service_names=nae-kmip HTTP/1.1\r\nHost: ...\r\nConnection: Close\r\n\r\n";sleep 1) | openssl s_client -connect ...**.:443

---

HTTP/1.1 200 OK

Date: Wed, 06 Nov 2024 17:34:10 GMT

Content-Type: application/json; charset=UTF-8

Content-Length: 73

Connection: close

X-Krakend: Version 2.2.0

X-Krakend-Completed: false

X-Processing-Time: 0.000031

X-Request-Id: 7f2830f5-9e4a-4d80-9bc4-1fe2cce2f02f

Expires: Wed, 06 Nov 2024 16:34:10 GMT

Cache-Control: no-cache

X-Frame-Options: DENY

Strict-Transport-Security: max-age=31536000; includeSubdomains; preload

X-XSS-Protection: 1; mode=block

Client-Verify: NONE

X-Content-Type-Options: nosniff

X-Permitted-Cross-Domain-Policies: none

Feature-Policy: geolocation 'none'; camera 'none'; speaker 'none'; microphone 'none';

Referrer-Policy: strict-origin-when-cross-origin

Expect-CT: enforce, max-age=72000

Content-Security-Policy: default-src 'self' blob:;base-uri 'self'; form-action 'self'; frame-ancestors 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; font-src 'self' data:; object-src 'none'; img-src 'self' data:;

Cache-Control: no-store

{"status":"started","services":[{"name":"nae-kmip","status":"started"}]}

closed