This is strange behavior, especially when using TCP vport which should not manipulate the HTTP server responses in any way. Also the fact that only Chrome experiences the issue is perplexing.
I would think that source IP Persistence would assist in either scenario. Which method did you use?
A packet capture with the preferred configuration may be useful in diagnosing this further.