
This is because if this header is missing, the websocket client will populate this header as "http://...", which is incorrect if we are using secure connection (in which this header should be "https://..."). Change-Id: I441946dc168db645744da093e215f65fa1ca3637 Related-Bug: #1762511