#1475 CLI options for HTTP connection
Closed: migrated 3 years ago by dmoluguw. Opened 8 years ago by edewata.

Currently if the CLI does not receive a response from the server (e.g. incorrectly using SSL port for non-secure connection) it will wait until timeout (1 minute) and retry the connection three more times, so the total will be 4 minutes.

$ pki -c Secret123 -n caadmin kra-user-cert-add pkidbuser --serial 0x1
ERROR: CA subsystem not available
CA server URI [http://kra.example.com:8080]: http://ca.example.com:8443
Jul 09, 2015 5:06:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:06:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
Jul 09, 2015 5:07:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:07:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
Jul 09, 2015 5:08:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: I/O exception (org.apache.http.NoHttpResponseException) caught when processing request to {}->http://ca.example.com:8443: The target server failed to respond
Jul 09, 2015 5:08:15 PM org.apache.http.impl.client.DefaultHttpClient tryExecute
INFO: Retrying request to {}->http://ca.example.com:8443
NoHttpResponseException: ca.example.com:8443 failed to respond

There should be options to change this behavior:

  • --http-timeout <timeout in seconds> (default: 30 seconds)
  • --http-retries <count> (default: 0)

Proposed milestone: 10.3


Per CS/DS meeting of 07/13/2015: 10.3

Metadata Update from @edewata:
- Issue set to the milestone: UNTRIAGED

7 years ago

Dogtag PKI is moving from Pagure issues to GitHub issues. This means that existing or new
issues will be reported and tracked through Dogtag PKI's GitHub Issue tracker.

This issue has been cloned to GitHub and is available here:
https://github.com/dogtagpki/pki/issues/2034

If you want to receive further updates on the issue, please navigate to the
GitHub issue and click on Subscribe button.

Thank you for understanding, and we apologize for any inconvenience.

Metadata Update from @dmoluguw:
- Issue close_status updated to: migrated
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata