The behavior of SstHttpConnectionManager (used by the 'http' and 'https' transport configurations) has changed: http connections that are closed by the client are no longer retried by the server when sending the response.

In http, a closed connection cannot be re-established from a server to the client. This previously existing behavior lead to http server workers trying to re-establish a connection until a timeout was received. In certain network setups, especially involving non-local firewalls, this timeout is potentially very long. When all workers are stuck waiting for a timeout, the server becomes unresponsive.

However, because of this behavior, the use of the 'http' and 'https' transport schemes would work in earlier versions of VAST.

Users who are instantiating SstHttpClient using the 'http' or 'https' transport scheme rather than the 'httpl' or 'httpsl' transport scheme, will experience errors from the client when trying to establish a connection. Although this was functioning in earlier versions of VAST, the 'http' and 'https' transport schemes are intended for server configurations only. Due to the change in the behavior of SstHttpConnectionManager>>#connectionFor:, this will no longer work.