Cloud Docs Home > F5 Application Services Proxy Index

Release Notes for the F5 Application Services Proxy


Added Functionality

  • Ability to store ephemeral data in a non-persistent datastore.
  • Health monitoring of pool members using active and passive health checks. The health monitor can use the ephemeral datastore to reduce the frequency of health probes that forward-proxy ASP instances must issue for the active health checks.
  • User-configurable event handlers can manipulate transaction lifecycle objects, like client HTTP request and real server HTTP response.
  • Reduced container size requirements.

Bug Fixes

  • Added schema to validate ASP configuration.
  • Updated documentation and corrected broken links.


  • Active health checks only support HTTP probes.
  • Event handlers can only require Node.js core modules; Event handlers cannot require or use external NPM modules.


Added Functionality

  • Uses a schema to validate the configuration.
  • A Kubernetes watch file allows for the dynamic reconfiguration of the virtual servers (not available for marathon).
  • Has the ability to use user-developed Express middleware modules.
  • Proxies and load balances HTTP and TCP apps in the Mesos/Marathon and Kubernetes environments.
  • Dynamically discovers tasks associated with Marathon apps. The Application Services Proxy acts as a reverse proxy for each app task.
  • Provides default middleware agents: Header Manipulation, Load Balancing, Connection Management, Forwarder.
  • Delivers a rich set of L4 and L7 stats in Splunk compatible format.
  • Supports configuring CA certificate for sending stats to HTTPS server.
  • Supports virtual-servers to share a bind-port in shared-listen mode (not available for marathon).


  • All load balancing uses the Round Robin algorithm.
  • In the connection limiting algorithm when the accept token reaches 0, the server will continue to accept connections from the backlog until the event loop ends.