cURL snippets fail on Windows due to Single Quote

[mzhukovs]

Describe the bug
@umeshp7 @shreys7
#72 #92
this causes a problem on Windows machines; by pasting the cURL generated code snipped into a Windows Command Prompt, you get the misleading error message:

curl: (1) Protocol "'https" not supported or disabled in libcurl

Which is just due to the single quotes, and can be fixed only by using double quotes.

see here: https://stackoverflow.com/questions/6884669/curl-1-protocol-https-not-supported-or-disabled-in-libcurl

Much like you have the option to change the line continuation character from \ to ^ in the Settings there, I think the single vs. double quote should also be an option.

As a bonus, would be nice if Postman detected that the machine is Windows and defaulted to ^ and " in the settings accordingly.

To Reproduce
Paste any resulting cURL snippet into a win cmd prompt

[someshkoli]

@umeshp7 the line breaker option is available in the options but i guess is not set in the postmanapp.

[JannemanDev]

This is generated by Postman using cURL but still causes trouble:
curl -L -X POST "https://localhost:5443/connect/token" -H 'Content-Type: application/x-www-form-urlencoded' --data-urlencode 'client_id=m2m.client' --data-urlencode 'scope=weatherapi.read' --data-urlencode 'client_secret=SuperSecretPassword' --data-urlencode 'grant_type=client_credentials'

should be

curl -L -XPOST "https://localhost:5443/connect/token" -H "Content-Type: application/x-www-form-urlencoded" --data-urlencode "client_id=m2m.client&scope=weatherapi.read&client_secret=SuperSecretPassword&grant_type=client_credentials"

Notice the removal of the space between -X and POST! Also the data needs double quotes.

Here's another example generated by cURL:
curl -L -X GET "https://localhost:5445/WeatherForecast" -H 'Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjlCMTQ3MUM0MDI4MUVDMDdBMUZFRjZCNzkwNEFDNTYzIiwidHlwIjoiYXQrand0In0.eyJuYmYiOjE2MDk2ODA1MjIsImV4cCI6MTYwOTY4NDEyMiwiaXNzIjoiaHR0cHM6Ly9sb2NhbGhvc3Q6NTQ0MyIsImF1ZCI6IndlYXRoZXJhcGkiLCJjbGllbnRfaWQiOiJtMm0uY2xpZW50IiwianRpIjoiNzJBMUM1OTNEOEU1MDI2Q0Q1Mjc3M0RFNjkyQ0QyQjEiLCJpYXQiOjE2MDk2ODA1MjIsInNjb3BlIjpbIndlYXRoZXJhcGkucmVhZCJdfQ.YI3HXCNl4Ov8-SjBXp9VftxfBZ4ZiHojMbBaNsH0y5ol2wc-ZsY3ua97m0XWmiiP3BZgJYN7hz8_gvpI03NXTgSIbMPxN7zubyiYQZ2XRjUZTukCevAjBvcPimqxBoJ4lC1UzbGnK-VjIdPWGKeSf3MOcQRl2K0Trw66qXqmjAkYC7K4t_qWw7p5UNY7QPY0t872YaaRLNlnqQnJBMbVhs9HESsk1reF3HQ8Oi-HwD5ikty9fhBK61h409RPeNljeW4dTxCSPU3AetA13VFSSL_M0ONqhpyE7pjrd1ghNMF0tOC1pqRSrQzOd7VBtscaMAAEupuNRzu_r-qIK4ROxw'

should be

curl -L -XGET "https://localhost:5445/WeatherForecast" -H "Authorization: Bearer eyJhbGciOiJSUzI1NiIsImtpZCI6IjlCMTQ3MUM0MDI4MUVDMDdBMUZFRjZCNzkwNEFDNTYzIiwidHlwIjoiYXQrand0In0.eyJuYmYiOjE2MDk2ODA1MjIsImV4cCI6MTYwOTY4NDEyMiwiaXNzIjoiaHR0cHM6Ly9sb2NhbGhvc3Q6NTQ0MyIsImF1ZCI6IndlYXRoZXJhcGkiLCJjbGllbnRfaWQiOiJtMm0uY2xpZW50IiwianRpIjoiNzJBMUM1OTNEOEU1MDI2Q0Q1Mjc3M0RFNjkyQ0QyQjEiLCJpYXQiOjE2MDk2ODA1MjIsInNjb3BlIjpbIndlYXRoZXJhcGkucmVhZCJdfQ.YI3HXCNl4Ov8-SjBXp9VftxfBZ4ZiHojMbBaNsH0y5ol2wc-ZsY3ua97m0XWmiiP3BZgJYN7hz8_gvpI03NXTgSIbMPxN7zubyiYQZ2XRjUZTukCevAjBvcPimqxBoJ4lC1UzbGnK-VjIdPWGKeSf3MOcQRl2K0Trw66qXqmjAkYC7K4t_qWw7p5UNY7QPY0t872YaaRLNlnqQnJBMbVhs9HESsk1reF3HQ8Oi-HwD5ikty9fhBK61h409RPeNljeW4dTxCSPU3AetA13VFSSL_M0ONqhpyE7pjrd1ghNMF0tOC1pqRSrQzOd7VBtscaMAAEupuNRzu_r-qIK4ROxw"

My settings were: