transfer a URL

-L, --location
       (HTTP/HTTPS) If the server reports that the requested page  has  moved  to  a  different  location
       (indicated  with  a Location: header and a 3XX response code), this option will make curl redo the
       request on the new place. If used together with -i, --include or  -I,  --head,  headers  from  all
       requested pages will be shown. When authentication is used, curl only sends its credentials to the
       initial host. If a redirect takes curl to a different host, it won't  be  able  to  intercept  the
       user+password.  See  also  --location-trusted  on  how to change this. You can limit the amount of
       redirects to follow by using the --max-redirs option.

       When curl follows a redirect and the request is not a plain GET (for example POST or PUT), it will
       do  the  following  request  with a GET if the HTTP response was 301, 302, or 303. If the response
       code was any other 3xx code, curl will re-send the following request  using  the  same  unmodified
       method.

-k, --insecure
       (SSL)  This option explicitly allows curl to perform "insecure" SSL connections and transfers. All
       SSL connections are attempted to be made secure by using the CA certificate  bundle  installed  by
       default. This makes all connections considered "insecure" fail unless -k, --insecure is used.

       See this online resource for further details: http://curl.haxx.se/docs/sslcerts.html

-A, --user-agent <agent string>
       (HTTP) Specify the User-Agent string to send to the HTTP server. Some badly done CGIs fail if this
       field isn't set to "Mozilla/4.0". To encode blanks in the string, surround the string with  single
       quote marks. This can also be set with the -H, --header option of course.

       If this option is set more than once, the last one will be the one that's used.

-n, --netrc
       Makes  curl  scan  the .netrc (_netrc on Windows) file in the user's home directory for login name
       and password. This is typically used for FTP on UNIX. If used with HTTP,  curl  will  enable  user
       authentication.  See  netrc(4) or ftp(1) for details on the file format. Curl will not complain if
       that file doesn't have the right permissions (it should not be either world-  or  group-readable).
       The environment variable "HOME" is used to find the home directory.

       A  quick  and  very  simple  example  of how to setup a .netrc to allow curl to FTP to the machine
       host.domain.com with user name 'myself' and password 'secret' should look similar to:

       machine host.domain.com login myself password secret