AVI Load Balancer Rewrites Backend HTTP 302 Redirect URL Port Before Forwarding to Client

Products

• VMware Avi Load Balancer

Issue/Introduction

When an L7 Virtual Service is configured with multiple listening ports (for example, 1443, 2443, and 3443), requests sent to secondary ports such as 2443 or 3443 and receive an HTTP 302 redirect response from the backend server. 

However, while forwarding the redirect response to the client, the AVI Load Balancer rewrites the redirect URL and replaces the original backend response port with the primary Virtual Service port (for example, 1443).

 

 

 

Environment

AVI Load Balancer: All versions

 

Cause

For Virtual Services configured with multiple listening ports, the AVI Load Balancer maintains the port list in ascending order internally. 

When "Rewrite Server Redirects to HTTPS" is enabled on the Virtual Service Application Profile, and the request HostName matches the HostName in the backend-generated 302 redirect URL, AVI rewrites the redirect response and replaces the original redirect port with the first port in the sorted Virtual Service port list.

 

Resolution

As a workaround we can Disable "Rewrite Server Redirects to HTTPS" option in Application profile.

This will be addressed in the Future releases from the Product side.