Thanks for all the responses.
After wireshark tracing, turns out to be a client side issue. Garbage packets/packets in wrong order are being sent by Chrome in rare occasions.
Switching to HTTP/2 which seems to not have this issue in Chrome.
After wireshark tracing, turns out to be a client side issue. Garbage packets/packets in wrong order are being sent by Chrome in rare occasions.
Switching to HTTP/2 which seems to not have this issue in Chrome.
