libcurl-url.3 5.2 KB

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