Using curl to test POST data

Basic request passing variables as POST

Use --data or -d option to pass variables to the page.

$ curl -d "user=mylogin&pass=mypass&foo=bar&biz=bash" http://www.mydomain.com/mypage/

Request using basic authentication

Use --user or -u option.

$ curl -u mylogin:mypass -d "user=mylogin&pass=mypass&foo=bar&biz=bash" http://www.mydomain.com/mypage/

Request using Windows integrated authentication

Add --ntlm option.

$ curl -u mylogin:mypass --ntlm -d "user=mylogin&pass=mypass&foo=bar&biz=bash" http://www.mydomain.com/mypage/

Special characters in username or password

Escape special characters with back slash.

$ curl -u mylogin:myp\&ss --ntlm -d "user=mylogin&pass=mypass&foo=bar&biz=bash" http://www.mydomain.com/mypage/

Storing arguments in a text file

Content of file, saved as curlargs.txt:

-d foo=bar&biz=bash http://localhost/mytestpage.html

Run curl using contents of curlargs.txt (in a bash shell):

$ cat curlargs.txt | xargs -n3 curl

Sending request headers

> curl -H "X-MyHeader: 123" www.google.com

The argument is either -H or --header followed by header name, colon, and header value.

For example, to send an Accept request-header for JSON data: -H "Accept: application/json".

To view the request that is sent add the -v option to curl.

Handling quotes in POST data

Problem: The value of the -d or --data argument (typically a JSON string) contains either a single or double quote:

# Error is thrown when it hits the first quote in the ''title'' string.
curl -d '{ "id": "6650", "title": "A record title containing 'quotes'."}' http://mydomain.com/path/to/page/

Solution: Use the @ character to read the data from a separate file.

Curl arguments stored in curargs.txt:

-d @jsondata.txt http://mydomain.com/path/to/page/

Contents of jsondata.txt:

{ "id": "6650", "title": "A record title containing 'quotes'."}

Then pass the contents of the two files to curl with

$ cat curlargs.txt | xargs -n3 curl

Sending POST requests to Django projects

Because of Cross Site Request Forgery protection in Django, POST requests have to include a CSRF token generated by the Django app.

It's not really practical or safe to generate the token so it can be used with curl.

Instead right above the Django view that is being called, place an CSRF exemption:

from django.views.decorators.csrf import csrf_exempt

@csrf_exempt
def my_view(request):
    return HttpResponse('Hello world')

It's possible to pass the token with curl:

curl
 -X POST
 -d "email=test@test.com&a=1&csrfmiddlewaretoken=<inserttoken>"
 --cookie "csrftoken=[as above]"
 http://127.0.0.1:8083/registrations/register/

It's also possible to use --header "X-CSRFToken: <token>" instead of including it in the form data.

Following redirects

$ curl -L -XPOST -d "foo=bar&biz=bash" http://dev-server.com

• -L location Tells curl to reattempt the get if the server reports that the page is at a different location (301 and 302 responses)
• -XPOST Explicitly use the POST method (as opposed to the -d option which implicitly uses POST. (man.cx manual pages)

This happens with Symfony, which sends a 301 response with its controllers.,

N.B. This did not work on the first attempt with Symfony. Not sure if it's not a solution, or if I was doing something wrong.