1.2. Document Change History

Added information for X-Forwarded-Port header (see Section 4.1.3, “Create Load Balancer”).

Added note about deleting a health monitor of any type (refer to Section 4.11, “Monitors”).

Added information about request body for GET and PUT requests for Content Caching (refer to Section 4.14, “Content Caching”).

Added information about rate limits and Repose (refer to Section 3.7, “Limits”).

Modified call to get the current rate limits for the account (refer to Section 3.7.3, “Determining Limits Programmatically”).

Added note about the authentication token's expiration time being formatted differently in the US and UK (refer to Section 3.1.2, “Retrieving the Authentication Token” ).

Added note about port attribute for Create Load Balancer (refer to Section 4.1.3, “Create Load Balancer”).

Added Half-Closed support for load balancers (refer to Section 4.1.3, “Create Load Balancer” and Section 4.1.4, “Update Load Balancer Attributes”).

Updated note for specifying attributes for connection throttling (refer to Section 4.13.2, “Throttle Connections”).

Updated Section 3.6, “Paginated Collections”.

Added timeout option to load balancer. Refer to Section 4.1.3, “Create Load Balancer” for the description of timeout and its usage.

Updated Shared IPs information with samples for IPv4/IPv6 combinations. Refer to Section 4.1.3, “Create Load Balancer”.

Added section for Health Monitoring based logging with ATOM and API formatted feeds. Refer to Section 4.4.5, “View Node Service Events”.

Updated auth response examples (refer to Section 3.1.2, “Retrieving the Authentication Token”).

Added information on pricing and service level. See Section 1.4, “Pricing and Service Level” for details.

Corrected our date/time format from RFC 822 to RFC 8601. See Section 3.9, “Date/Time Format” for details.

Added the ability to share UDP and TCP based load balancer protocols on the same port. See Section 3.10, “Compatible Shared Load Balancing Protocols” for details.

Updated example for List Load Balancers Response: JSON to show that it returns an integer for nodeCount rather than a string. See Section 4.1.1, “List Load Balancers” for details.

Added note about proper certificate ordering. See Section 4.17, “SSL Termination” for details.

Updated Section 3.9, “Date/Time Format” XML example for Modify Node. See Section 4.4.3, “Modify Nodes” for details.

Updated description for content caching. See Section 4.14, “Content Caching” for details.

Updated description for SOURCE_IP session persistence mode. See Section 4.12.1, “Manage Session Persistence” for details.

Updated information on the secondary nodes failover feature. See Section 2.5.1, “Active Health Monitor” and Section 4.11, “Monitors” for details.

Updated for Auth 2.0 (refer to Section 3.1, “Authentication”).

An optional hostHeader field is supported for the HTTP and HTTPS health monitor. See Section 4.11.1.2, “Monitor HTTP and HTTPS”.

Added additional information on the secondary nodes failover feature. See Section 2.5.1, “Active Health Monitor”, Section 4.4.3, “Modify Nodes”, and Section 4.11.1.1, “Monitor Connections” for details.

Added tables of required/optional attributes for POST and PUT requests.

Updated links for API documentation (see Section 1.3, “Additional Resources”).

Added Metadata API calls to access metadata for a specified node (see Section 4.18, “Metadata”).

Added support for content caching (see Section 4.14, “Content Caching”).

Updated service catalog information for authentication (see Section 3.1.2, “Retrieving the Authentication Token”).

Updated information for the nodeaddress query parameter for finding out whether any load balancer for an account has a specific node attached to it: the parameter can specify the node using either a domain name or IP address (see Section 4.1.1, “List Load Balancers”).

Updated examples for load balancing protocols to include SFTP (see Section 4.15.1, “List Load Balancing Protocols”).

Updated response examples for load balancer usage to contain SSL data (see Section 4.9.1, “List Usage”).

Added new SOURCE_IP session persistence mode (see Section 4.12.1, “Manage Session Persistence”).

Updated note for customers who are transferring certain types of Personally Identifiable Information (PII) and added information for x-forwarded-proto and x-forwarded-for headers (see Section 4.17, “SSL Termination”).

List Load Balancers call now displays the node count (see Section 4.1.1, “List Load Balancers”).

Allow users to specify primary and secondary nodes for their load balancers (see Section 4.4.2, “Add Nodes”).

Added API call List Allowed Domains so users can see the list of allowable domains (see Section 4.6.1, “List Allowed Domains”).

Valid domain names can be used to add nodes (see Section 4.4.2, “Add Nodes” and Section 4.6.1, “List Allowed Domains”).

Added API call List Billable Load Balancers to list an account's billable load balancers for a date range. (see Section 4.9, “Usage Reports”).

Added new protocols such as TCP Client First, DNS, UDP, and MySQL (see Section 4.15, “Protocols”).

Fixed "View Load Balancing SSL Termination Configuration Response: JSON" example in Section 4.17, “SSL Termination”.

Metadata can be assigned to each load balancer (see Section 4.18, “Metadata”).

Added note about ServiceNet in Section 3.2, “Service Access/Endpoints”.

Added note to customers describing who should not use SSL Termination in Section 4.17, “SSL Termination”.

Corrected note below Example 4.81 "View Load Balancing SSL Termination Configuration Response: JSON" about wrapping the key/certificates in a newline character in Java in Section 4.17, “SSL Termination”.

Updated endpoints for authentication for Section 3.1.1, “Geographic Endpoints”.

Updated Auth Response examples for Section 3.1.2, “Retrieving the Authentication Token” to show the latest service catalog.

Updated Section 3.7.3, “Determining Limits Programmatically” to fix limits and absolutelimits API calls.

Fixed Create Load Balancer (Required Attributes) Request: XML example to be consistent with the JSON example in Section 4.1.3, “Create Load Balancer”.

Added Section 4.17, “SSL Termination” for new SSL termination feature.

Deleted section 2.5.1 "Passive Health Monitor (No Longer Available)" since the passive health monitor has been disabled.

Updated information in Table 4.2, “Virtual IP Types” to reflect that a default IPV6 is being provisioned when creating a load balancer.

Added support for Auth 1.1 in Section 3.1, “Authentication”.

Updated information for Section 3.2, “Service Access/Endpoints”.

A default IPV6 is being provisioned when creating a load balancer. Refer to Table 4.2, “Virtual IP Types”. (This was turned off in Release 1.6.13 as a temporary mitigation strategy.)

Added Section 4.3, “List Load Balancer Stats”.

Updated information inTable 4.2, “Virtual IP Types”.

Updated Section 4.4.1, “List Nodes” with note about weight attributes.

Updated section 2.5.1 "Passive Health Monitor (No Longer Available)".

Added Section 3.9, “Date/Time Format”.

Updated Section 4.1.1, “List Load Balancers” with information for query parameter nodeaddress.

AddedSection 4.2, “Error Page”.

Updated examples as needed to match the latest API.

Updated Atom examples.

UpdatedSection 3.7.2, “Absolute Limits”.

Added basic TCP load balancing to allow customers to load balance traffic for any TCP-based prototcol. See Section 4.15, “Protocols”.

An X-Forwarded-For (XFF) HTTP header is now automatically inserted for all inbound HTTP requests. See Section 4.1.3, “Create Load Balancer”.

Added programmatic support for determining Cloud Load Balancer source addresses. See Section 4.1.2, “List Load Balancer Details” andSection 4.1.3, “Create Load Balancer”.

Added support for batch delete of Load Balancers, Nodes, Virtual IPs, and Access List Entries. See Section 4.1.5, “Remove Load Balancer”,Section 4.4.4, “Remove Nodes”, Section 4.8, “Remove Virtual IP”, andSection 4.10.1, “Manage Access Lists”, respectively.

Updated Section 3.7.2, “Absolute Limits” and added absolutelimits API call to Section 3.7.3, “Determining Limits Programmatically” to return the current absolute limits for the account.

Updated examples to match the current API.

Added service endpoint for London (LON) region.

Added support for accessing the Authentication Service, based on whether your account is US-based or UK-based.

Added support for IPv6.

Added details to support initial GA release.

Revised code samples and formatting to address initial beta feedback.

Initial release for public beta.