libcurl-url.3 5.4 KB

123456789101112131415161718192021222324252627282930313233343536373839404142434445464748495051525354555657585960616263646566676869707172737475767778798081828384858687888990919293949596979899100101102103104105106107108109110111112113114115116117118119120121122123124125126127128129130131132133134135136137138139140141142143144145146147148
  1. .\" **************************************************************************
  2. .\" * _ _ ____ _
  3. .\" * Project ___| | | | _ \| |
  4. .\" * / __| | | | |_) | |
  5. .\" * | (__| |_| | _ <| |___
  6. .\" * \___|\___/|_| \_\_____|
  7. .\" *
  8. .\" * Copyright (C) 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. .\" * SPDX-License-Identifier: curl
  22. .\" *
  23. .\" **************************************************************************
  24. .TH libcurl 3 "10 Sep 2018" "libcurl" "libcurl"
  25. .SH NAME
  26. libcurl-url \- URL interface overview
  27. .SH DESCRIPTION
  28. The URL interface provides functions for parsing and generating URLs.
  29. .SH INCLUDE
  30. You still only include <curl/curl.h> in your code.
  31. .SH CREATE
  32. Create a handle that holds URL info and resources with \fIcurl_url(3)\fP:
  33. .nf
  34. CURLU *h = curl_url();
  35. .fi
  36. .SH CLEANUP
  37. When done with it, clean it up with \fIcurl_url_cleanup(3)\fP
  38. .nf
  39. curl_url_cleanup(h);
  40. .fi
  41. .SH DUPLICATE
  42. When you need a copy of a handle, just duplicate it with \fIcurl_url_dup(3)\fP:
  43. .nf
  44. CURLU *nh = curl_url_dup(h);
  45. .fi
  46. .SH PARSING
  47. By setting a URL to the handle with \fIcurl_url_set(3)\fP, the URL is parsed
  48. and stored in the handle. If the URL is not syntactically correct it will
  49. return an error instead.
  50. .nf
  51. rc = curl_url_set(h, CURLUPART_URL,
  52. "https://example.com:449/foo/bar?name=moo", 0);
  53. .fi
  54. The zero in the fourth argument is a bitmask for changing specific features.
  55. If successful, this stores the URL in its individual parts within the handle.
  56. .SH REDIRECT
  57. When a handle already contains info about a URL, setting a relative URL will
  58. make it "redirect" to adapt to it.
  59. .nf
  60. rc = curl_url_set(h, CURLUPART_URL, "../test?another", 0);
  61. .fi
  62. .SH "GET URL"
  63. The \fBCURLU\fP handle represents a URL and you can easily extract that with
  64. \fIcurl_url_get(3)\fP:
  65. .nf
  66. char *url;
  67. rc = curl_url_get(h, CURLUPART_URL, &url, 0);
  68. curl_free(url);
  69. .fi
  70. The zero in the fourth argument is a bitmask for changing specific features.
  71. .SH "GET PARTS"
  72. When a URL has been parsed or parts have been set, you can extract those
  73. pieces from the handle at any time.
  74. .nf
  75. rc = curl_url_get(h, CURLUPART_FRAGMENT, &fragment, 0);
  76. rc = curl_url_get(h, CURLUPART_HOST, &host, 0);
  77. rc = curl_url_get(h, CURLUPART_PASSWORD, &password, 0);
  78. rc = curl_url_get(h, CURLUPART_PATH, &path, 0);
  79. rc = curl_url_get(h, CURLUPART_PORT, &port, 0);
  80. rc = curl_url_get(h, CURLUPART_QUERY, &query, 0);
  81. rc = curl_url_get(h, CURLUPART_SCHEME, &scheme, 0);
  82. rc = curl_url_get(h, CURLUPART_USER, &user, 0);
  83. rc = curl_url_get(h, CURLUPART_ZONEID, &zoneid, 0);
  84. .fi
  85. Extracted parts are not URL decoded unless the user also asks for it with the
  86. \fICURLU_URLDECODE\fP flag set in the fourth bitmask argument.
  87. Remember to free the returned string with \fIcurl_free(3)\fP when you are done
  88. with it!
  89. .SH "SET PARTS"
  90. A user set individual URL parts, either after having parsed a full URL or
  91. instead of parsing such.
  92. .nf
  93. rc = curl_url_set(urlp, CURLUPART_FRAGMENT, "anchor", 0);
  94. rc = curl_url_set(urlp, CURLUPART_HOST, "www.example.com", 0);
  95. rc = curl_url_set(urlp, CURLUPART_PASSWORD, "doe", 0);
  96. rc = curl_url_set(urlp, CURLUPART_PATH, "/index.html", 0);
  97. rc = curl_url_set(urlp, CURLUPART_PORT, "443", 0);
  98. rc = curl_url_set(urlp, CURLUPART_QUERY, "name=john", 0);
  99. rc = curl_url_set(urlp, CURLUPART_SCHEME, "https", 0);
  100. rc = curl_url_set(urlp, CURLUPART_USER, "john", 0);
  101. rc = curl_url_set(urlp, CURLUPART_ZONEID, "eth0", 0);
  102. .fi
  103. Set parts are not URL encoded unless the user asks for it with the
  104. \fICURLU_URLENCODE\fP flag.
  105. .SH "CURLU_APPENDQUERY"
  106. An application can append a string to the right end of the query part with the
  107. \fICURLU_APPENDQUERY\fP flag to \fIcurl_url_set(3)\fP.
  108. Imagine a handle that holds the URL "https://example.com/?shoes=2". An
  109. application can then add the string "hat=1" to the query part like this:
  110. .nf
  111. rc = curl_url_set(urlp, CURLUPART_QUERY, "hat=1", CURLU_APPENDQUERY);
  112. .fi
  113. It will even notice the lack of an ampersand (&) separator so it will inject
  114. one too, and the handle's full URL will then equal
  115. "https://example.com/?shoes=2&hat=1".
  116. The appended string can of course also get URL encoded on add, and if asked to
  117. URL encode, the encoding process will skip the '=' character. For example,
  118. append "candy=N&N" to what we already have, and URL encode it to deal with the
  119. ampersand in the data:
  120. .nf
  121. rc = curl_url_set(urlp, CURLUPART_QUERY, "candy=N&N",
  122. CURLU_APPENDQUERY | CURLU_URLENCODE);
  123. .fi
  124. Now the URL looks like
  125. .nf
  126. https://example.com/?shoes=2&hat=1&candy=N%26N
  127. .fi
  128. .SH AVAILABILITY
  129. The URL API was introduced in libcurl 7.62.0.
  130. A URL with a literal IPv6 address can be parsed even when IPv6 support is not
  131. enabled.
  132. .SH "SEE ALSO"
  133. .BR curl_url "(3), " curl_url_cleanup "(3), " curl_url_get "(3), "
  134. .BR curl_url_dup "(3), " curl_url_set "(3), " curl_url_strerror "(3), "
  135. .BR CURLOPT_URL "(3)"