Use Curl to access the HTTPS site and log in (the results returned by HTTP are particularly clear)

Develop web sites, without testing. The web site now has the HTTPS protocol enabled to enhance security. The so-called HTTPS, which is HTTP text, is transmitted in the SSL protocol. Using the Curl command line to test the HTTPS site is a useful feature, writing a script, you can do functional testing.

Assume that the Ubuntu system is running an HTTPS site, written in Cppcms, Nginx configured SSL certificate, through the fastcgi and cppcms written by the background process connected together.

First step, install:

[Plain]View PlainCopyprint?

1. Apt-get Install Curl

My Ubuntu is 13.04, so the version of Curl installed is very new, the following command checks the version number and other information:

[Plain]View PlainCopyprint?

1. Curl-v
2. Curl 7.29.0 (X86_64-PC-LINUX-GNU) libcurl/7.29.0 openssl/1.0.1c zlib/1.2.7 libidn/1.25 librtmp/2.3
3. Protocols:dict file ftp FTPs Gopher HTTP HTTPS IMAP imaps LDAP ldaps POP3 pop3s rtmp rtsp smtp Smtps telnet tftp
4. Features:gss-negotiate IDN IPv6 largefile NTLM ntlm_wb SSL libz TLS-SRP

We can see that SSL is enabled and the OpenSSL version is 1.0.1c.

The second step is to access the HTTP site:

[Plain]View PlainCopyprint?

1. Curl http://www.baidu.com
2. <! DOCTYPE html><!--STATUS ok-->Copyprint?
   2. Curl-v http://www.baidu.com
   4. * About-to-connect () to www.baidu.com Port (#0)
   6. * Trying 61.135.169.125 ...
   8. * Connected to Www.baidu.com (61.135.169.125) port (#0)
   10. > get/http/1.1
   12. > user-agent:curl/7.29.0
   14. > Host:www.baidu.com
   16. > Accept: */*
   18. >
   20. < http/1.1 OK
   22. < date:wed, 13:55:45 GMT
   24. < server:bws/1.0
   26. < content-length:10437
   28. < Content-type:text/html;charset=utf-8
   30. < Cache-control:private
   32. < set-cookie:bdsvrtm=24; path=/
   34. < set-cookie:h_ps_pssid=2757_1457_2704_2726_1788_2249_2702; path=/; Domain=.baidu.com
   36. < set-cookie:baiduid=5e81f8e70c5de6edb5c24088e3e56359:fg=1; expires=wed, 03-jul-43 13:55:45 GMT; path=/; Domain=.baidu.com
   38. < expires:wed, 13:55:45 GMT
   40. < p3p:cp= "OTI DSP COR IVA our IND COM"
   42. < connection:keep-alive
   44. <
   45. <! doctype html><!--status ok-->

   
   Such detailed information is displayed. The-v parameter is useful, and is usually turned on when debugging.

   If you want to see only the header information, use-I instead of-V.

   Fourth step, visit the local HTTPS site

   [Plain]View PlainCopyprint?
   1. Curl--insecure Https://localhost/your_site/login_page
   3. <! DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 transitional//en" "Http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd ">
   6. <meta http-equiv= "Content-type" content= "text/html; Charset=utf-8 ">
   7. <meta http-equiv= "Pragma" content= "No-cache" >
   8. <meta http-equiv= "Cache-control" content= "No-cache" >

   ---insecure indicates that the validation step is ignored.

   I tried to specify the Server.crt file with the--cacert option, which is the file that my Nginx uses. But the error. So just ignore it and forget it.

   Fifth step, call the HTTPS login API

   [Plain]View PlainCopyprint?
   2. Curl-v--insecure-d "[Email protected]&pwd=123456&language=en" Https://localhost/your_site/login
   4. * About-to-connect () to localhost port 443 (#0)
   6. * Trying 127.0.0.1 ...
   8. * Connected to localhost (127.0.0.1) port 443 (#0)
   10. * Successfully set certificate Verify locations:
   12. * Cafile:none
   14. Capath:/etc/ssl/certs
   16. * SSLv3, TLS handshake, Client hello (1):
   18. * SSLv3, TLS handshake, Server Hello (2):
   20. * SSLv3, TLS handshake, CERT (11):
   22. * SSLv3, TLS handshake, Server key Exchange (12):
   24. * SSLv3, TLS handshake, Server finished (14):
   26. * SSLv3, TLS handshake, Client key Exchange (16):
   28. * SSLv3, TLS change cipher, Client hello (1):
   30. * SSLv3, TLS handshake, finished (20):
   32. * SSLv3, TLS change cipher, Client hello (1):
   34. * SSLv3, TLS handshake, finished (20):
   36. * SSL Connection using Ecdhe-rsa-aes256-sha
   38. * Server Certificate:
   40. * SUBJECT:C=AU; St=some-state; O=internet widgits Pty LTD
   42. * Start date:2013-06-02 07:24:53 GMT
   44. * Expire date:2014-06-02 07:24:53 GMT
   46. * ISSUER:C=AU; St=some-state; O=internet widgits Pty LTD
   48. * SSL Certificate Verify result:self signed certificate, continuing anyway.
   50. > Post/your_site/login http/1.1
   52. > user-agent:curl/7.29.0
   54. > Host:localhost
   56. > Accept: */*
   58. > content-length:51
   60. > content-type:application/x-www-form-urlencoded
   62. >
   64. * Upload completely sent off:51 out of Wuyi bytes
   66. < http/1.1 OK
   68. < server:nginx/1.5.1
   70. < date:wed, 14:02:38 GMT
   72. < content-type:text/html; Charset=utf-8
   74. < transfer-encoding:chunked
   76. < connection:keep-alive
   78. < x-powered-by:cppcms/1.0.3
   80. < set-cookie:cml_session=518b7fc5117e87bce28f2444; max-age=36000; path=/; Version=1
   82. <
   84. * Connection #0 to host localhost-left intact
   86. {"Message": "Login succeeded!", "status": 0, "value": ""}

   
   -D "... & ..." Parameters are sent via the Post method. The server eventually replies to a JSON-formatted string that indicates a successful login. And get the Cml_session value, which is the cookie.

   The sixth step is to use cookies to access HTTP Web pages. The following pages only require HTTP access, providing the correct cookie.

   [Plain]View PlainCopyprint?
   2. Curl-v--cookie "cml_session=518b7fc5117e87bce28f2444" Http://localhost/your_site/home
   4. * About to connect () to localhost port (#0)
   6. * Trying 127.0.0.1 ...
   8. * Connected to localhost (127.0.0.1) port (#0)
   10. > Get/your_site/home http/1.1
   12. > user-agent:curl/7.29.0
   14. > Host:localhost
   16. > Accept: */*
   18. > cookie:cml_session=518b7fc5117e87bce28f2444
   20. >
   22. < http/1.1 OK
   24. < server:nginx/1.5.1
   26. < date:wed, 14:06:43 GMT
   28. < content-type:text/html; Charset=utf-8
   30. < transfer-encoding:chunked
   32. < connection:keep-alive
   34. < x-powered-by:cppcms/1.0.3
   36. <
   40. <! DOCTYPE HTML PUBLIC "-//W3C//DTD XHTML 1.0 transitional//en" "Http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd ">
   46. <meta http-equiv= "Content-type" content= "text/html; Charset=utf-8 ">
   48. <meta http-equiv= "Pragma" content= "No-cache" >
   50. <meta http-equiv= "Cache-control" content= "No-cache" >
   52. <meta http-equiv= "Expires" content= "0" >
   54. <TITLE>CML cloud</title>
   56. <link type= "Text/css" href= ". /style/reset.css "rel=" stylesheet "/>
   58. <link type= "Text/css" href= ". /style/style.css "rel=" stylesheet "/>

   
   http://blog.csdn.net/csfreebird/article/details/9237925

   Use Curl to access the HTTPS site and log in (the results returned by HTTP are particularly clear)