HTTP URL fragments are sent to server. Regression of 7.28.1 and possibly 7.20.0 bugfixes. #4412
I did this
Both requests resulted with 404 HTTP code. Tried 2 different OS and lib versions.
Possible regression of https://sourceforge.net/p/curl/bugs/1159/
When performing the same commands with curl 7.29.0 it works as expected and I am getting HTTP 200 codes at the end.
I expected the following
curl 7.64.0 (x86_64-pc-linux-gnu) libcurl/7.64.0 OpenSSL/1.1.1b zlib/1.2.11 libidn2/2.0.5 libpsl/0.20.2 (+libidn2/2.0.5) libssh/0.8.6/openssl/zlib nghttp2/1.36.0 librtmp/2.3
curl 7.66.0 (x86_64-redhat-linux-gnu) libcurl/7.66.0 OpenSSL/1.0.1e-fips zlib/1.2.3 c-ares/1.15.0 libssh2/1.8.2 nghttp2/1.6.0
CentOS release 6.10 (Final)
The text was updated successfully, but these errors were encountered:
The parser would check for a query part before fragment, which caused it to do wrong when the fragment contains a question mark. Extended test 1560 to verify. Reported-by: Alex Konev Fixes #4412