[ERROR] Error in request #22: Get : unsupported protocol scheme ""

[sherlocksecurity]

When running with windows, the following error is displayed in all hosts

[ERROR] Error in request #22: Get: unsupported protocol scheme ""

Usage: race-the-web_2.0.1_win64.exe config.toml

Sample TOML file:
[[requests]]
# Use the POST request method
method = "POST"
# Set the URL target. Any valid URL is accepted, including ports, https, and parameters.
url = "https://in.com/mwaccount/profiles/password/forgot"
# Set the request body.
body = "utf8=%E2%9C%93&authenticity_token=gMHC3AxOL2VVoN3Fgos%2FAgvwVHkkxhauUo%2BpBcWY9J2QTsKSQYNHc7wYnA8LttkUCJkPiLGd%2FkWzYNXrQlaEBA%3D%3D&forgot_password%5Bemail_address%5D=old-pond-1796%40ninja.com&forgot_password%5Bredirect_uri%5D=https%3A%2F%2Fin.com%2Fmwaccount%2F&forgot_password%5Bmobile_app%5D=false"
# Set the cookie values to send with the request to this target. Must be an array.
cookies = ["_mwaccount_session=BAh7B0kiD3Nlc3Npb25faWQGOgZFVEkiJWYxMzg0ZDE3NjI4YWNjNjM0NGQ0ODJhMzUxZmJhMTI3BjsAVEkiEF9jc3JmX3Rva2VuBjsARkkiMUVJOEFUazNOYUJicHVFSEtpVDNtRmdOcFcvR1ZXK2pyNGU5ODdvZk9jSms9BjsARg%3D%3D--d0bab2a87c26ceb5dbac9ea1fd04b63df48f0f1f","s_ecid=MCMID%7C13723289101733544942239425349042073252"]
# Set custom headers to send with the request to this target. Must be an array.
headers = ["Content-Type: application/x-www-form-urlencoded","Origin: https://in.com","Content-Length: 319","Referer: https://in.com/mwaccount/profiles/password/"]
# Do not follow redirects
redirects = false

[TheHackerDev]

Hm. So it has something to do with a protocol (i.e. https, http, ftp, etc; sent at the beginning of the URL like https://...). Because you have redirects disabled, that tells me that it's in the request, but not in any of the responses. Can you look through all the URIs being passed in the request to ensure that they are properly formatted/spelled?

Another issue might be the first body parameter's value (utf8=%E2%9C%93). The URL-encoded part decodes to a checkmark character which might odd. That's not likely the issue here though.

Also, can you please try sending the request in a single curl request instead and seeing if you get any errors with that?