Refer to the exhibit. A developer is using cURL to test connectivity to a webpage. The request times out after 10 seconds. The developer tested connectivity by using Ping and can open a TCP socket to the remote server by using Telnet. Other users confirm that they can access the webpage from their device. The developer has SSH access to the remote server and runs commands to troubleshoot. What causes the issue?
The issue is likely due to application-layer security features on the remote server blocking the connection. This can happen if the server has security policies in place that specifically block certain types of requests, such as those made by cURL. Even though the developer can ping the server and establish a TCP connection via Telnet, these methods do not test the same application-layer protocols and security features that cURL and HTTPS use. Therefore, the server's application-layer security settings are the probable cause of the timeout.
The server may have increased security that is blocking the cURL request2. Even though the developer can ping the server and open a TCP socket with Telnet, the application layer security could still block specific types of connections, like cURL12.
C. Application-layer security features on the remote server block the connection.
Curl is using certification key, so there is some sort of TLS Client Authentication configured in the Remote Server. My answer would be C.
Think its B: Firewall rules on the remote server block the client on port 443. • The server is up and running since other users can access the webpage. • The client can connect via Telnet and SSH, meaning general network connectivity is fine. • The issue is specific to HTTPS traffic (port 443), suggesting that a firewall rule is blocking the client’s IP.