For https connections, if this is true, it will fail to connect if the TLS certificate can not be
verified. Setting this to false will skip this check and allow the connection to continue anyway.
When the HttpRequest is constructed from a HttpClient, it will inherit the value from the client
instead of using the = true here. You can change this value any time before you call send (which
is done implicitly if you call waitForCompletion).
Prior to this, it always used the global (but undocumented) defaultVerifyPeer setting, and sometimes
even if it was true, it would skip the verification. Now, it always respects this local setting.
For https connections, if this is true, it will fail to connect if the TLS certificate can not be verified. Setting this to false will skip this check and allow the connection to continue anyway.
When the HttpRequest is constructed from a HttpClient, it will inherit the value from the client instead of using the = true here. You can change this value any time before you call send (which is done implicitly if you call waitForCompletion).