200-901 · Question #578
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…
The correct answer is D. HTTPS proxy configured on the remote server blocks the connection. The cURL timeout after a successful TCP connection, coupled with other users accessing the webpage, suggests an application-layer issue specific to the developer's request, likely due to an HTTPS proxy configuration on the remote server.
Question
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?
Options
- AConnectivity from the remote server back to the client is down.
- BFirewall rules on the remote server block the client on port 443.
- CApplication-layer security features on the remote server block the connection.
- DHTTPS proxy configured on the remote server blocks the connection.
How the community answered
(26 responses)- A12% (3)
- B23% (6)
- C4% (1)
- D62% (16)
Why each option
The cURL timeout after a successful TCP connection, coupled with other users accessing the webpage, suggests an application-layer issue specific to the developer's request, likely due to an HTTPS proxy configuration on the remote server.
Ping and Telnet connectivity indicate that two-way IP connectivity is functioning between the client and the remote server.
Since Telnet can successfully open a TCP socket on port 443, firewall rules on the remote server are not blocking the initial connection establishment.
While application-layer security could block connections, a misconfigured HTTPS proxy is a more specific and common cause for such symptoms, where a TCP connection establishes but no valid application data exchange occurs.
A cURL timeout after a successful TCP connection (confirmed by Telnet) and working service for other users strongly indicates an application-layer problem. An HTTPS proxy configured on the remote server could be blocking or improperly processing the developer's specific cURL request, causing the application-level timeout while lower-layer connectivity is intact.
Concept tested: Troubleshooting application-layer connectivity issues
Topics
Community Discussion
No community discussion yet for this question.