Internal HTTP stack has been rewritten

The internal HTTP stack has been rewritten to support pre-2.20 features and HTTP retries.

This enables pre-2.20 lost features like Kerberos Support, NTLM single Sign-on or Client certificate.

GDC is also able to retry when network errors occur. This was already the case in previous (late MR) versions, but now it may retry in more situations (ex: in case of HTTP error 500). This can be useful if your network is not too reliable and sometimes messages may be discarded before reaching GAS or returning to GDC. You can now configure how GDC will retry:

Figure: HTTP Retries section of Connection tab

The figure is a screen shot of the Genero Desktop Client in Administrative Mode with the HTTP Retries section highlighted in the Connection Tab.

The entry "1;1;1;2;2;2;4;4;4" means that GDC will retry 9 times. GDC will wait 1 second between the first three errors, then 2 seconds between the next three, and 4 seconds between the last three. GDC will then wait a maximum of 21 seconds before showing an error message.

Note:

This is the time GDC waits AFTER the system / network returns an error, not the complete waiting time. For instance, if the system needs time to answer (ex: connection timed out), GDC will wait:

  1. for the system
  2. for the configured wait time

GDC now shows some information in the systray icon when there is an HTTP connection issue.