libcurl-url.3 5.1 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137
  1. .\" **************************************************************************
  2. .\" * _ _ ____ _
  3. .\" * Project ___| | | | _ \| |
  4. .\" * / __| | | | |_) | |
  5. .\" * | (__| |_| | _ <| |___
  6. .\" * \___|\___/|_| \_\_____|
  7. .\" *
  8. .\" * Copyright (C) 1998 - 2020, Daniel Stenberg, <daniel@haxx.se>, et al.
  9. .\" *
  10. .\" * This software is licensed as described in the file COPYING, which
  11. .\" * you should have received as part of this distribution. The terms
  12. .\" * are also available at https://curl.se/docs/copyright.html.
  13. .\" *
  14. .\" * You may opt to use, copy, modify, merge, publish, distribute and/or sell
  15. .\" * copies of the Software, and permit persons to whom the Software is
  16. .\" * furnished to do so, under the terms of the COPYING file.
  17. .\" *
  18. .\" * This software is distributed on an "AS IS" basis, WITHOUT WARRANTY OF ANY
  19. .\" * KIND, either express or implied.
  20. .\" *
  21. .\" **************************************************************************
  22. .TH libcurl 3 "10 Sep 2018" "libcurl" "libcurl url interface"
  23. .SH NAME
  24. libcurl-url \- URL interface overview
  25. .SH DESCRIPTION
  26. The URL interface provides a set of functions for parsing and generating URLs.
  27. .SH INCLUDE
  28. You still only include <curl/curl.h> in your code. Note that the URL API was
  29. introduced in 7.62.0.
  30. .SH CREATE
  31. Create a handle that holds URL info and resources with \fIcurl_url(3)\fP:
  32. CURLU *h = curl_url();
  33. .SH CLEANUP
  34. When done with it, clean it up with \fIcurl_url_cleanup(3)\fP:
  35. curl_url_cleanup(h);
  36. .SH DUPLICATE
  37. When you need a copy of a handle, just duplicate it with \fIcurl_url_dup(3)\fP:
  38. CURLU *nh = curl_url_dup(h);
  39. .SH PARSING
  40. By "setting" a URL to the handle with \fIcurl_url_set(3)\fP, the URL is parsed
  41. and stored in the handle. If the URL is not syntactically correct it will
  42. return an error instead.
  43. .nf
  44. rc = curl_url_set(h, CURLUPART_URL,
  45. "https://example.com:449/foo/bar?name=moo", 0);
  46. .fi
  47. The zero in the fourth argument is a bitmask for changing specific features.
  48. If successful, this stores the URL in its individual parts within the handle.
  49. .SH REDIRECT
  50. When a handle already contains info about a URL, setting a relative URL will
  51. make it "redirect" to adapt to it.
  52. rc = curl_url_set(h, CURLUPART_URL, "../test?another", 0);
  53. .SH "GET URL"
  54. The `CURLU` handle represents a URL and you can easily extract that with
  55. \fIcurl_url_get(3)\fP:
  56. char *url;
  57. rc = curl_url_get(h, CURLUPART_URL, &url, 0);
  58. curl_free(url);
  59. The zero in the fourth argument is a bitmask for changing specific features.
  60. .SH "GET PARTS"
  61. When a URL has been parsed or parts have been set, you can extract those
  62. pieces from the handle at any time.
  63. .nf
  64. rc = curl_url_get(h, CURLUPART_HOST, &host, 0);
  65. rc = curl_url_get(h, CURLUPART_SCHEME, &scheme, 0);
  66. rc = curl_url_get(h, CURLUPART_USER, &user, 0);
  67. rc = curl_url_get(h, CURLUPART_PASSWORD, &password, 0);
  68. rc = curl_url_get(h, CURLUPART_PORT, &port, 0);
  69. rc = curl_url_get(h, CURLUPART_PATH, &path, 0);
  70. rc = curl_url_get(h, CURLUPART_QUERY, &query, 0);
  71. rc = curl_url_get(h, CURLUPART_FRAGMENT, &fragment, 0);
  72. .fi
  73. Extracted parts are not URL decoded unless the user also asks for it with the
  74. CURLU_URLDECODE flag set in the fourth bitmask argument.
  75. Remember to free the returned string with \fIcurl_free(3)\fP when you're done
  76. with it!
  77. .SH "SET PARTS"
  78. A user set individual URL parts, either after having parsed a full URL or
  79. instead of parsing such.
  80. .nf
  81. rc = curl_url_set(urlp, CURLUPART_HOST, "www.example.com", 0);
  82. rc = curl_url_set(urlp, CURLUPART_SCHEME, "https", 0);
  83. rc = curl_url_set(urlp, CURLUPART_USER, "john", 0);
  84. rc = curl_url_set(urlp, CURLUPART_PASSWORD, "doe", 0);
  85. rc = curl_url_set(urlp, CURLUPART_PORT, "443", 0);
  86. rc = curl_url_set(urlp, CURLUPART_PATH, "/index.html", 0);
  87. rc = curl_url_set(urlp, CURLUPART_QUERY, "name=john", 0);
  88. rc = curl_url_set(urlp, CURLUPART_FRAGMENT, "anchor", 0);
  89. .fi
  90. Set parts are not URL encoded unless the user asks for it with the
  91. `CURLU_URLENCODE` flag.
  92. .SH "APPENDQUERY"
  93. An application can append a string to the right end of the query part with the
  94. `CURLU_APPENDQUERY` flag to \fIcurl_url_set(3)\fP.
  95. Imagine a handle that holds the URL `https://example.com/?shoes=2`. An
  96. application can then add the string `hat=1` to the query part like this:
  97. .nf
  98. rc = curl_url_set(urlp, CURLUPART_QUERY, "hat=1", CURLU_APPENDQUERY);
  99. .fi
  100. It will even notice the lack of an ampersand (`&`) separator so it will inject
  101. one too, and the handle's full URL will then equal
  102. `https://example.com/?shoes=2&hat=1`.
  103. The appended string can of course also get URL encoded on add, and if asked to
  104. URL encode, the encoding process will skip the '=' character. For example,
  105. append `candy=N&N` to what we already have, and URL encode it to deal with the
  106. ampersand in the data:
  107. .nf
  108. rc = curl_url_set(urlp, CURLUPART_QUERY, "candy=N&N",
  109. CURLU_APPENDQUERY | CURLU_URLENCODE);
  110. .fi
  111. Now the URL looks like
  112. .nf
  113. https://example.com/?shoes=2&hat=1&candy=N%26N`
  114. .fi
  115. .SH "SEE ALSO"
  116. .BR curl_url "(3), " curl_url_cleanup "(3), " curl_url_get "(3), "
  117. .BR curl_url_dup "(3), " curl_url_set "(3), " CURLOPT_URL "(3), "