Describe the bug
If you start a simple server with QUIC and wait kinda like 12 hours, and try to fetch resource, you'll get this:
2025-04-07T08:21:29.781024Z ERROR salvo_core::conn::quinn::builder:233: unable to send response to connection peer error=h3::Error { code: H3_REQUEST_CANCELLED }
2025-04-07T08:21:29.781038Z ERROR salvo_core::conn::quinn::builder:243: unable to send data to connection peer error=h3::Error { kind: NotReady, code: : None }
2025-04-07T08:21:29.781057Z ERROR salvo_core::conn::quinn::builder:91: process request failed error=Custom { kind: Other, error: "failed to finish stream : quic transport error: NotReady" }
...
2025-04-07T08:21:30.567540Z ERROR salvo_core::conn::quinn::builder:243: unable to send data to connection peer error=h3::Error { code: H3_REQUEST_CANCELLED }
2025-04-07T08:21:30.567597Z ERROR salvo_core::conn::quinn::builder:243: unable to send data to connection peer error=h3::Error { kind: NotReady, code: : None }
But, if you refetch your resource after 1-3 seconds, you will get all that you want.
Desktop (please complete the following information):
- OS: Linux
- Browser: Firefox
- Version:
salvo v0.77 (also was in 0.70+)
Describe the bug
If you start a simple server with QUIC and wait kinda like 12 hours, and try to fetch resource, you'll get this:
But, if you refetch your resource after 1-3 seconds, you will get all that you want.
Desktop (please complete the following information):
salvov0.77 (also was in 0.70+)