mirror of
https://git.haproxy.org/git/haproxy.git/
synced 2026-01-30 14:31:08 +01:00
28cb36613b
If a regex to match the PATH_INFO parameter is configured, it systematically fails if a newline or a null character is present in the URL-decoded path. So, from the moment there is at least a "%0a" or a "%00" in the request path, we always fail to get the PATH_INFO parameter and all the decoded path is used for the SCRIPT_NAME parameter. It is probably not the expected behavior. Because, most of time, these characters are not expected at all in a path, an error is now triggered when one of these characters is found in the URL-decoded path before trying to execute the path_info regex. However, this test is not performed if there is no regex configured. Note that in reality, the newline character is only a problem when HAProxy is complied with pcre or pcre2 library and conversely, the null character is only a problem for the libc's regex library. But both are always excluded to avoid any inconsistency depending on compile options. An alternative, not implemented yet, is to replace these characters by another one. If someone complains about this behavior, it will be re-evaluated. This patch must be backported to all versions supporting the FastCGI applications, so to 2.1 for now.