New Features Now Available for Rackspace Cloud Load Balancers

We’re pleased to announce a major feature update for our Cloud Load Balancers product.   Priority given to these features was largely based on feedback received from customers through our product feedback site.   If you have suggestions on how we can improve this offering further, please let us know.

These new features are now available:

–    Basic TCP Load Balancing – This new feature allows customers to load balance traffic for any TCP-based protocol.

–    X-Forwarded-For Header for HTTP Traffic – The cloud load balancer now automatically inserts an X-Forwarded-For HTTP header for all inbound HTTP requests.  This header will contain the actual source address of the client, which many web applications are already designed to use when determining the source address for a request.  All newly created and existing HTTP load balancers now have this header in the HTTP request.

–    Programmatic Support for Determining Cloud Load Balancer Source Addresses – API users are now able to programmatically derive the source addresses of our cloud load balancers.  This new feature is useful for customers who are automating the deployment of infrastructure and need to determine the IP addresses of requests coming from our load balancers for the purpose of creating more robust firewall rules.

–    Batch Delete of Load Balancers, Nodes, Virtual IPs and Access List Entries – API users are now able to delete multiple items from all list entities, which improves the efficiency of client interactions with the service.

For more information on how to use the new features available in our API, please refer to the Cloud Load Balancers API Developer Guide.

Josh leads product development for the Cloud Platform Product Line where he is responsible for product management, engineering, and operations for the Cloud Sites, Load Balancing, Database and DNS product offerings.


  1. Hi ,

    How can we change the following terms




    In order to get Passthrough Email working for internal users it looks like we will need to get the internal servers configured to add an X-Orig-To header when forwarding messages (as the external servers seem to do).

    Please help me to make these changes in rackspace.


Please enter your comment!
Please enter your name here