mirror of
https://github.com/haproxy/haproxy.git
synced 2026-04-15 21:59:41 -04:00
22731762d9
Ben Kallus also noticed that we preserve leading zeroes on content-length values. While this is totally valid, it would be safer to at least trim them before passing the value, because a bogus server written to parse using "strtol(value, NULL, 0)" could inadvertently take a leading zero as a prefix for an octal value. While there is not much that can be done to protect such servers in general (e.g. lack of check for overflows etc), at least it's quite cheap to make sure the transmitted value is normalized and not taken for an octal one. This is not really a bug, rather a missed opportunity to sanitize the input, but is marked as a bug so that we don't forget to backport it to stable branches. A combined regtest was added to h1or2_to_h1c which already validates end-to-end syntax consistency on aggregate headers. |
||
|---|---|---|
| .. | ||
| 1k.txt | ||
| acl_cli_spaces.vtc | ||
| agents.acl | ||
| converters_ipmask_concat_strcmp_field_word.map | ||
| converters_ipmask_concat_strcmp_field_word.vtc | ||
| default_rules.vtc | ||
| del_header.vtc | ||
| except-forwardfor-originalto.vtc | ||
| forwarded-header-7239.vtc | ||
| h1or2_to_h1c.vtc | ||
| http_after_response.vtc | ||
| http_return.vtc | ||
| ifnone-forwardfor.vtc | ||
| lf-file.txt | ||
| map_redirect-be.map | ||
| map_redirect.map | ||
| map_redirect.vtc | ||
| map_regm_with_backref.map | ||
| map_regm_with_backref.vtc | ||
| normalize_uri.vtc | ||
| path_and_pathq.vtc | ||
| restrict_req_hdr_names.vtc | ||
| strict_rw_mode.vtc | ||