mirror of
https://github.com/haproxy/haproxy.git
synced 2026-07-10 17:55:32 -04:00
75e013727c
thttpd forwards the CGI's stderr to the client *ahead* of its stdout: the socket receives the HTTP status line, then any stderr log line, and only then the CGI headers, turning the log line into a bogus response header; on an error path the same mechanism could push garbage in front of the "Status:" header and corrupt the response entirely. All diagnostics are already carried by the response itself (die()'s body, the in-band "warning:" line with git's captured error), so the duplicated stderr logging brings nothing and only risks breaking the channel it leaks into: drop it, and state the constraint in a comment above die() so it doesn't come back. The usage text for a bad command line is folded into the 500 response body, which is also what a shell user sees when testing by hand. |
||
|---|---|---|
| .. | ||
| base64 | ||
| coccinelle | ||
| flags | ||
| gdb | ||
| h2 | ||
| haring | ||
| hpack | ||
| ncpu | ||
| patchbot | ||
| phash | ||
| plug_qdisc | ||
| poll | ||
| qpack | ||
| sslkeylogger | ||
| tcploop | ||
| term_events | ||
| trace | ||
| udp | ||