Added support for providing data-raw according to #8.

My reasoning for the proposed solution is that they should never be present simultaneously, and if data-raw isn't present, then go for default behavior with the -d|data-option, giving data-raw a slight precedence over data.

Just wondering how you want to handle the --location flag. With cURL, it means "follow any redirects" but the Laravel Http client does this by default.

My thinking is to just silently accept and discard it so that it doesn't throw an error like this:

Thoughts? I'm happy to add this "feature" if you're ok with the idea of just ignoring it.

Added support for providing data-raw according to #8.

My reasoning for the proposed solution is that they should never be present simultaneously, and if data-raw isn't present, then go for default behavior with the -d|data-option, giving data-raw a slight precedence over data.

Added support for providing data-raw according to #8.

My reasoning for the proposed solution is that they should never be present simultaneously, and if data-raw isn't present, then go for default behavior with the -d|data-option, giving data-raw a slight precedence over data.

When copying request from Chrome DevTools the options --insecure and --compressed are sometimes present, and was not recognized by the package.

The --insecure option should primarily be present when posting/fetching data from a non-SSL endpoint. The --compressed option indicates that cURL accepts any encoded response, equivalent to CURLOPT_ENCODING = ""

I added support for these two in the options gatherer. They won't have any effect on the standard HTTP call, thus are simply ignored.

Removed notes about #8

This PR extracts the URL query string to the data array in the Laravel HTTP client.

For example,

curl "https://api.postmarkapp.com/messages/[email protected]&count=50&offset=0&tag=welcome&status=sent&todate=2015-01-12&fromdate=2015-01-01" -X GET

currently yields this HTTP request:

Http::get('https://api.postmarkapp.com/messages/[email protected]&count=50&offset=0&tag=welcome&status=sent&todate=2015-01-12&fromdate=2015-01-01');

Which technically works but it not very readable. Now it will instead output this:

Http::get('https://api.postmarkapp.com/messages/outbound', [
        'recipient' => '[email protected]',
        'count' => '50',
        'offset' => '0',
        'tag' => 'welcome',
        'status' => 'sent',
        'todate' => '2015-01-12',
        'fromdate' => '2015-01-01',
    ]);

Which makes query string parameters much more readable and easy to edit the individual values in the code.

NOTE: This uses PHP's parse_url. This creates a refactoring opportunity in App/Models/Request on line 65 to use it to get the Http Basic Auth username and password instead of exploding the raw URL string.

Many tools such as postman use data-raw. Maybe worth adding support for this, esp for json requests?

curl --request POST 'https://api.com' \
--header 'Accept: application/json' \
--header 'Content-Type: application/json' \
--data-raw '{
    "messages": [
        "a",
        "b",
        "c"
    ]
}'

There's no Laravel output, feel free to contribute one, but we do convert to PHP's cURL library https://curlconverter.com/php/

The website also links to other projects doing the same thing. This is the 3rd project called "curl converter" that I know of. We only link to projects that work on the client, there are other projects (including this one) that we don't link to because they upload curl commands to a server they control, which would allow them to silently nefariously log the curl command and if you paste a command with a cookie or auth token in it, that would be bad.

https://github.com/curlconverter/curlconverter

The --data-raw option takes some interpretation. The curl docs do not state that it is mutually exclusive from --data. From a quick tests, it seems curl merges the data when called with both --data and --data-raw.

With that said, the common use case for --data-raw seems to be independent. When passed alone, this is the exact data to send in the request payload.

This PR adds support for --data-raw to the specification above - parsing it as form data when mixed with --data or sending it as the raw body when used independently.

Hi there, this is a really useful project thank you!

I've just tried with one of my more troublesome POST queries I have to make and I'm having a problem getting it to convert.

I need to make a POST request to a URL with the following as the payload. This is taken directly as a copy from Chrome using devtools.

The Raw format

Print=Print&selection=aerodromeOrder&aerodrome=eick&Basket=false&icao=eick&check=on&order=eickei+&order=f1780614+&order=f1738132+&order=b1738132+&order=f1928002+&order=f1736502+&order=b1736502+&order=f1736540+&order=f1736509+&order=b1736509+&order=f1736520+&order=b1736520+&order=f1736511+&order=b1736511+&order=f1736512+&order=b1736512+&order=f1736518+&order=b1736518+&order=f1736521+&order=b1736521+&order=f1736523+&order=f1736513+&order=b1736513+&order=f1736515+&order=b1736515+&order=f1736536+&order=b1736536+&order=f1896451+&order=b1896451+&order=f1736525+&order=b1736525+&order=f1758356+

Image from chrome dev tools:

As you can see there are multiple order keys in the data payload.

However when I try and use this package to convert this to Laravel HTTP format, only the last order key survives.

Whats the best way to deal with multiple keys having the same name?

This was the original request I tried to convert, I've just removed some excessive headers.

curl 'https://viewer.flightsupport.com/servlet/PrintServlet' \
  -H 'Content-Type: application/x-www-form-urlencoded' \
  -H 'Cookie: REDACTED' \
  -H 'Origin: https://viewer.flightsupport.com' \
  -H 'Pragma: no-cache' \
  -H 'Referer: https://viewer.flightsupport.com/frames/home.jsp' \
  -H 'Sec-Fetch-Dest: document' \
  -H 'Sec-Fetch-Mode: navigate' \
  -H 'Sec-Fetch-Site: same-origin' \
  -H 'Sec-Fetch-User: ?1' \
  -H 'Upgrade-Insecure-Requests: 1' \
  -H 'User-Agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/106.0.0.0 Safari/537.36' \
  --data-raw 'Print=Print&selection=aerodromeOrder&aerodrome=eick&Basket=false&icao=eick&check=on&order=eickei+&order=f1780614+&order=f1738132+&order=b1738132+&order=f1928002+&order=f1736502+&order=b1736502+&order=f1736540+&order=f1736509+&order=b1736509+&order=f1736520+&order=b1736520+&order=f1736511+&order=b1736511+&order=f1736512+&order=b1736512+&order=f1736518+&order=b1736518+&order=f1736521+&order=b1736521+&order=f1736523+&order=f1736513+&order=b1736513+&order=f1736515+&order=b1736515+&order=f1736536+&order=b1736536+&order=f1896451+&order=b1896451+&order=f1736525+&order=b1736525+&order=f1758356+'

Would be great if it could also support for php curl to Http facade. e.g.

$ch = curl_init(); curl_setopt($ch, CURLOPT_URL, 'https://www.example.com/includes/api.php'); curl_setopt($ch, CURLOPT_POST, 1); curl_setopt($ch, CURLOPT_POSTFIELDS, http_build_query( array( 'action' => 'GetProducts', // See https://developers.whmcs.com/api/authentication 'username' => 'IDENTIFIER_OR_ADMIN_USERNAME', 'password' => 'SECRET_OR_HASHED_PASSWORD', 'pid' => '1', 'responsetype' => 'json', ) ) ); curl_setopt($ch, CURLOPT_RETURNTRANSFER, 1); $response = curl_exec($ch); curl_close($ch);

becomes

$result = Http::asForm()->post('https://www.example.com/includes/api.php', [ 'action' => 'GetProducts', 'username' => 'IDENTIFIER_OR_ADMIN_USERNAME', 'password' => 'SECRET_OR_HASHED_PASSWORD', 'pid' => '1', 'responsetype' => 'json', ])->json();

Following CURL request from Auth0 examples is not working:

curl --request POST --url https://signalcortex.us.auth0.com/oauth/token --header 'content-type: application/json' --data '{"client_id":"qwertyuiopasdfghqwertyuiopasdfgh","client_secret":"qwertyuiopasdfghqwertyuiopasdfghqwertyuiopasdfghqwertyuiopasdfgh","audience":"https://signalcortex.us.auth0.com/api/v2/","grant_type":"client_credentials"}'

From the Transitor API docs:

curl -v -X PUT \
  -H "Content-Type: audio/mpeg" \
  -T /path/to/your/audio/Episode1.mp3 \
  "upload_url_from_authorize_upload"

The Content-Type header and -T option can be replaced with withBody($contents, 'audio/mpeg') where $contents is the complete file contents. (Like via file_get_contents)

curl 'https://graphigo.prd.dlive.tv/' --data-binary '{"query":"query{userByDisplayName(displayname: "Potato") {username displayname avatar partnerStatus followers{totalCount}}}"}'

Currently backslashes (and possibly other characters) are being lost from values as they are passed through Artisan. These need to be escaped so they are preserved in the final output. An appropriately placed call to addslashes should to the trick.

Example curl command:

curl --request POST https://example.com/pdf/extract --header 'Content-Type: multipart/form-data' --form 'file=C:\Users\secret\files\007.pdf'

I have just tested the new genius feature to convert cURL call to Laravel HTTP request and faced with the issue, the "-c" option does not exist. This is the cookie file handling feature of the cURL function.

Example cURL call: curl -v -F [email protected] -c ./cookies.txt -o response.pdf https://www.szamlazz.hu/szamla/

Reference: https://docs.szamlazz.hu/#post-request