You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Next »

These are the highlights of new features or additions to existing features in v5.0.x. For the complete list of all changes see this JIRA Release Notes.

SPDY

SPDY is now implemented in core Traffic Server. SPDY is supported for both TLS (encrypted) and non-TLS access. Protocol sniffing is used to detect SPDY for non-encrypted connections and for TLS connections that do not do NPN negotiations. SPDY versions 3.0 and 3.1 are supported.

As part of this work the custom logging format tags pitag and piid were added to make it possible to log SPDY related information.

Cache Backwards Compatiility

Traffic Server can now run on caches created by previous versions of Traffic Server back to version 3.2.0. This is done by run time conversions when an object is read from the cache. All data written to the cache is written in the current cache format. Over time a cache will gradually be converted to more recent formats. Interally, objects are now written out with version information per object to make future compatibility easier. This means that although the cache format changed for 5.1.x, this should not invalidate any 5.0.X cache.

Backwards compatibilty for the cache will not be indefinitely extended. Traffic Server may remove support for cache formats that are for version of Traffic Server that are past end of support.

Server Session Sharing

Traffic Server supports sharing server sessions between clients. Previously this was done only for requests that matched both the fully qualified domain name and IP address. This remains the default but can be adjusted to match on either the IP address or the FQDN only.

Sessions with auth headers can be placed in to the server session pool (TS-2902).

Transparency Security Fix

Due to security issues the ability to use the client target address for the server address has been changed. The client supplied address is now checked against DNS results and if it does not match the request is not cached. The old (potenially unsafe) behavior can be done by setting proxy.config.http.use_client_target_addr to the value ``2``. (TS-2954)

TLS

Handling of ECDSA certificates was improved (TS-2893).

The cipher suite and protocol used by ATS as a client are now configurable (TS-2924).

SNI can be set for outbound connections from ATS (TS-2802)

sslheaders plugin added to inject information about connections in to the HTTP headers (TS-2957).

OCSP is now supported (TS-2367).

New Plugins

  • PageSpeed
  • SSL Headers

Minor Changes

  • traffic_line can now do VIA string decoding.
  • Many potential bugs were fixed by using Co-Verity and clang static checks.
  • Support for TOS settign on TCP sockets.
  • Log filters on IP fields works (TS-698).
  • Base string for stripe assignment allocation is now configurable (TS-3000).

Developer Changes

  • xptr was removed and replace with ats_scoped_str, ats_scoped_obj and ats_scoped_ptr for temporarily allocated resources.
  • The Doc header was changed to store per object version information.
  • traffic_manager was moved to the cmd directory.
  • libutils was merged in to libmgmt.
  • WebMgmtUtils moved to libmgmt.
  • No labels