Comments (1)
Quick update on this. First, the thread was brought there on the HTTP-WG mailing list:
https://lists.w3.org/Archives/Public/ietf-http-wg/2019JanMar/0056.html
Second among the ideas discussed (using PING+ACK, SETTINGS+ACK etc to measure the round trip time), all these only work with a cooperating client. A nasty client could very well refrain from ACKing and continue to send new streams or data for example. So the approach is nice to avoid truncating responses only.
For new streams and to be sure GOAWAY is taken into account, fixing a hard limit to last_stream_id + max_concurrent_streams + 1 guarantees a full round-trip was seen (GOAWAY is not ACKed), since this would imply that the closure that follows the GOAWAY was received to permit the last one to be sent. It could be used either alone, or in conjunction with RST_STREAM(REFUSED_STREAM) to figure when to really close. It also implicitly guarantees that the last data were received by the client. And it's not exclusive to the other ones above.
from haproxy.
Related Issues (20)
- src/cfgparse.c: null pointer dereference suspected by coverity HOT 5
- src/mux_quic.c: integer overflow suspected by coverity HOT 5
- src/cfgparse.c: TOCTOU violation suspected by coverity HOT 4
- src/mux_h1.c: integer overflow suspected by coverity HOT 2
- src/mux_h1.c: integer overflow suspected by coverity HOT 2
- src/haproxy.c: unused value suspected by coverity HOT 2
- src/quic_tx.c: integer overflow suspected by coverity HOT 6
- src/cfgparse.c: null pointer dereference suspected by coverity HOT 1
- Double "transfer-encoding: chunked" header return 502 error (terminal code PH)... HOT 9
- Assertion crash: bug condition "qcs->tx.fc.off_soft != qcs->tx.fc.off_real" matched at src/mux_quic.c:1707 HOT 2
- observe on-error is inconsistent with redispatch HOT 2
- src/pattern.c: double free is suspected by coverity HOT 6
- numerous coverity "overflow" errors HOT 9
- src/http_conv.c: dead code suspected by coverity
- HTTP connection upgrade to TCP seems broken since 2.4 HOT 5
- HAProxy / Logs missing for rejected HTTP responses from the backend when HTTP2 is used on frontend+backend
- How to Set Host Header Dynamically After Backend Server Selection in HAProxy HOT 1
- Request to Support for HTTP 429 Response Code in retry-on Directive HOT 11
- QUIC libressl Interop sometimes fails HOT 14
- cross compile failed HOT 2
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from haproxy.