transfer a URL

-f, --fail
       (HTTP)  Fail  silently  (no  output at all) on server errors. This is mostly done to better enable
       scripts etc to better deal with failed attempts. In normal cases  when  a  HTTP  server  fails  to
       deliver  a  document,  it  returns an HTML document stating so (which often also describes why and
       more). This flag will prevent curl from outputting that and return error 22.

       This method is not fail-safe and there are occasions where non-successful response codes will slip
       through, especially when authentication is involved (response codes 401 and 407).

-s, --silent
       Silent or quiet mode. Don't show progress meter or error messages.  Makes Curl mute.

-S, --show-error
       When used with -s it makes curl show an error message if it fails.

-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.

-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

-F, --form <name=content>
       (HTTP) This lets curl emulate a filled-in form in which a user has pressed the submit button. This
       causes curl to POST data using the Content-Type multipart/form-data according to  RFC  2388.  This
       enables  uploading  of binary files etc. To force the 'content' part to be a file, prefix the file
       name with an @ sign. To just get the content part from a file,  prefix  the  file  name  with  the
       symbol <. The difference between @ and < is then that @ makes a file get attached in the post as a
       file upload, while the < makes a text field and just get the contents for that text field  from  a
       file.