My apologies, I can see the issue is that it's valid for conn->data->state.up.query to be NULL, but at the time I assumed that query being NULL meant that there was a memory allocation failure. I think that this condition needs to also check if conn->data->state.up.query is not NULL and everything should just work? I won't have time to make this change and test it out for awhile, so someone else might need to do this.
- Allow missing queries, don't return NO_MEMORY error in such a case.
It is acceptable for there to be no specified query string, for example:
A regression bug in 1b443a7 caused this issue.
This is a partial fix for #4261.
Bug: #4261 (comment)
Analyzed-by: Samuel Surtees
I did this
I expected the following
curl 7.65.3 (x86_64-pc-win32) libcurl/7.65.3 OpenSSL/1.1.1c (Schannel) zlib/1.2.11 brotli/1.0.7 WinIDN libssh2/1.9.0 nghttp2/1.39.2
Both Windows 10 and Windows Server 2016
The text was updated successfully, but these errors were encountered: