Actions
Bug #7134
closed
Rudder API timeouts when passing wrong parameters
Pull Request:
Severity:
UX impact:
User visibility:
Effort required:
Priority:
Name check:
Fix check:
Regression:
Description
When one of the API parameters (token or version) is wrong, the request take a very long time to complete. It seems like a server-side timeout:
curl -v -k -X GET -H "Content-Type: application/json;charset=utf-8" --header "X-API-Token: SxedZNGsc6rxWXnHMKDPD13OTuoYPBXUZ" --header "X-API-Version: latest" "https://127.0.0.1:8381/rudder/api/nodes" * Trying 127.0.0.1... * Connected to 127.0.0.1 (127.0.0.1) port 8381 (#0) * Initializing NSS with certpath: sql:/etc/pki/nssdb * skipping SSL peer certificate verification * SSL connection using TLS_DHE_RSA_WITH_AES_128_GCM_SHA256 * Server certificate: * subject: CN=server.rudder.local * start date: Aug 19 12:42:02 2015 GMT * expire date: Aug 18 12:42:02 2019 GMT * common name: server.rudder.local * issuer: CN=server.rudder.local > GET /rudder/api/nodes HTTP/1.1 > User-Agent: curl/7.40.0 > Host: 127.0.0.1:8381 > Accept: */* > Content-Type: application/json;charset=utf-8 > X-API-Token: SxedZNGsc6rxWXnHMKDPD13OTuoYPBXUZ > X-API-Version: latest > < HTTP/1.1 401 Unauthorized < Date: Wed, 26 Aug 2015 09:09:05 GMT < Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips mod_wsgi/3.4 Python/2.7.5 < Content-Length: 381 < Content-Type: text/html; charset=iso-8859-1 < <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN"> <html><head> <title>401 Unauthorized</title> </head><body> <h1>Unauthorized</h1> <p>This server could not verify that you are authorized to access the document requested. Either you supplied the wrong credentials (e.g., bad password), or your browser doesn't understand how to supply the credentials required.</p> </body></html> * Connection #0 to host 127.0.0.1 left intact
Updated by 
Updated by 
Updated by 
Updated by
Actions