mirror of
http://git.haproxy.org/git/haproxy.git/
synced 2024-12-12 14:35:14 +00:00
ed2fd2daea
We've had several issues related to data transfers. First, if a client aborted an upload before the server started to respond, it would get a 502 followed by a 400. The same was true (in the other way around) if the server suddenly aborted while the client was uploading the data. The flags reported in the logs were misleading. Request errors could be reported while the transfer was stopped during the data phase. The status codes could also be overwritten by a 400 eventhough the start of the response was transferred to the client. The stats were also wrong in case of data aborts. The server or the client could sometimes be miscredited for being the author of the abort depending on where the abort was detected. Some client aborts could also be accounted as request errors and some server aborts as response errors. Now it seems like all such issues are fixed. Since we don't have a specific state for data flowing from the client to the server before the server responds, we're still counting the client aborted transfers as "CH", and they become "CD" when the server starts to respond. Ideally a "P" state would be desired. This patch should be backported to 1.4. |
||
|---|---|---|
| .. | ||
| design-thoughts | ||
| internals | ||
| acl.fig | ||
| architecture.txt | ||
| configuration.txt | ||
| gpl.txt | ||
| haproxy-en.txt | ||
| haproxy-fr.txt | ||
| haproxy.1 | ||
| lgpl.txt | ||
| proxy-protocol.txt | ||
| queuing.fig | ||