[pingora-proxy] Invalid frame header when upstream websocket connection

cloudflare / pingora

A library for building fast, reliable and evolvable network services.

Apache License 2.0

20.21k stars 1.1k forks source link

[pingora-proxy] Invalid frame header when upstream websocket connection #307

Open futurist opened 4 days ago

futurist commented 4 days ago

Describe the bug

The upstream connection is created, send some data, then encounter Invalid frame header, and the connection closed.

Pingora info

Please include the following information about your environment:

Pingora version: 0.2.0 Rust version: 1.79.0 Operating system version: Debian11

eaufavor commented 1 day ago

Do you have a minimal reproduce that you can share? Or maybe some tcpdump will help.

Also to clarify:

The upstream connection is created, send some data, then encounter Invalid frame header, and the connection closed.

The upstream (server) sent some date, then it encountered the invalid frame header and then it actively closed the connection due to the invalid frame?

futurist commented 17 hours ago

No, it's not easy to re-produce, I'll try to get the tcpdump next time when it's possible. I think it's the chrome's behavior to close the connection when encountered invalid frame.