Load balancer application rules not working after upgrading NSX to 6.4.6

Products

• VMware NSX for vSphere

Issue/Introduction

After upgrading the NSX for vSphere 6.4.6 the app rules is no longer working:

• Response headers from Load Balancer have lower case letters
• Load Balancer causes the back-end server to produce a HTTP 411 error

Cause

When HTTP(s) back-end servers are sitting behind a NSX Load Balancer as part of NSX edge, the clients are communicating with the back-end servers through the Load Balancer. Load Balancer sends headers in lower case, while in fact the servers have sent them in camel case. Example:
 

# expected originally send by the backend server header

"X-Deployment-Secret":"1ee5a70eaf011e4a7e89953d90774c791fea1e8cf8d1f8a7f3138fa19b2e8f72"

 

# mangled by the NSX edge LB header as seen by the client

"x-deployment-secret":"1ee5a70eaf011e4a7e89953d90774c791fea1e8cf8d1f8a7f3138fa19b2e8f72"

This is a known issue affecting VMware NSX for vSphere 6.4.6.

Resolution

Resolved in VMware NSX Data Center for vSphere 6.4.7, available at Broadcom Support Portal Downloads