//
// Copyright (c) 2023 Alan de Freitas (alandefreitas@gmail.com)
//
// Distributed under the Boost Software License, Version 1.0. (See accompanying
// file LICENSE_1_0.txt or copy at http://www.boost.org/LICENSE_1_0.txt)
//
// Official repository: https://github.com/boostorg/url
//

https://www.boost.org/doc/libs/master/libs/url/doc/html/[image:https://raw.githubusercontent.com/vinniefalco/url/master/doc/images/repo-logo.png[Boost.URL]]

[width="100%",cols="7%,66%,27%",options="header",]
|===
|Branch |https://github.com/boostorg/url/tree/master[`master`]
|https://github.com/boostorg/url/tree/develop[`develop`]

|https://www.boost.org/doc/libs/master/libs/url/doc/html/[Docs]
|https://www.boost.org/doc/libs/master/libs/url/doc/html/[image:https://img.shields.io/badge/docs-master-brightgreen.svg[Documentation]]
|https://www.boost.org/doc/libs/develop/libs/url/doc/html/[image:https://img.shields.io/badge/docs-develop-brightgreen.svg[Documentation]]

|https://github.com/[GitHub Actions]
|https://github.com/boostorg/url/actions/workflows/ci.yml[image:https://github.com/boostorg/url/actions/workflows/ci.yml/badge.svg?branch=master[CI]]
|https://github.com/boostorg/url/actions/workflows/ci.yml[image:https://github.com/boostorg/url/actions/workflows/ci.yml/badge.svg?branch=develop[CI]]

|https://drone.io/[Drone]
|https://drone.cpp.al/boostorg/url[image:https://drone.cpp.al/api/badges/boostorg/url/status.svg?ref=refs/heads/master[Build
Status]]
|https://drone.cpp.al/boostorg/url[image:https://drone.cpp.al/api/badges/boostorg/url/status.svg?ref=refs/heads/develop[Build
Status]]

|https://www.boost.org/development/tests/master/developer/summary.html[Matrix]
|http://www.boost.org/development/tests/master/developer/url.html[image:https://img.shields.io/badge/matrix-master-brightgreen.svg[Matrix]]
|http://www.boost.org/development/tests/develop/developer/url.html[image:https://img.shields.io/badge/matrix-develop-brightgreen.svg[Matrix]]

|https://codecov.io[Codecov]
|https://codecov.io/gh/boostorg/url/branch/master[image:https://codecov.io/gh/boostorg/url/branch/master/graph/badge.svg[codecov]]
|https://codecov.io/gh/boostorg/url/branch/develop[image:https://codecov.io/gh/boostorg/url/branch/develop/graph/badge.svg[codecov]]
|===

== Boost.URL

Boost.URL is a portable C++ library which provides containers and algorithms which model a "URL," more formally described using the
https://datatracker.ietf.org/doc/html/rfc3986[Uniform Resource Identifier (URI)]
specification (henceforth referred to as _rfc3986_).
A URL is a compact sequence of characters that identifies an abstract or physical resource.
For example, this is a valid URL:

[source]
----
https://www.example.com/path/to/file.txt?userid=1001&pages=3&results=full#page1
----

This library understands the grammars related to URLs and provides functionality to validate, parse, examine, and modify urls, and apply normalization or resolution algorithms.

=== Features

While the library is general purpose, special care has been taken to ensure that the implementation and data representation are friendly to network programs which need to handle URLs efficiently and securely, including the case where the inputs come from untrusted sources.
Interfaces are provided for using error codes instead of exceptions as needed, and most algorithms have the means to opt-out of dynamic memory allocation.
Another feature of the library is that all modifications leave the URL in a valid state.
Code which uses this library is easy to read, flexible, and performant.

Network programs such as those using Boost.Asio or Boost.Beast often encounter the need to process, generate, or modify URLs.
This library provides a very much needed modular component for handling these use-cases.

Boost.URL offers these features:

* C++11 as only requirement
* Fast compilation, few templates
* Strict compliance with _rfc3986_
* Containers that maintain valid URLs
* Parsing algorithms that work without exceptions
* Control over storage and allocation for URLs
* Support for `-fno-exceptions`, detected automatically
* Features that work well on embedded devices

[NOTE]
====
Currently, the library does not handle
https://www.rfc-editor.org/rfc/rfc3987.html[Internationalized Resource Identifiers (IRIs)].
These are different from URLs, come from Unicode strings instead of low-ASCII strings, and are covered by a separate specification.
====

=== Requirements

The library requires a compiler supporting at least C++11.

Aliases for standard types, such as _error_code_ or `string_view`, use their Boost equivalents.

Boost.URL works great on embedded devices.
It can be used in a way that avoids all dynamic memory allocations.
Furthermore, it offers alternative interfaces that work without exceptions if desired.

=== Tested Compilers

Boost.URL has been tested with the following compilers:

* clang: 3.8, 4, 5, 6, 7, 8, 9, 10, 11, 12
* gcc: 4.8, 4.9, 5, 6, 7, 8, 9, 10, 11
* msvc: 14.1, 14.2, 14.3

and these architectures: x86, x64, ARM64, S390x.

We do not test and support gcc 8.0.1.

=== Quality Assurance

The development infrastructure for the library includes these per-commit analyses:

* Coverage reports
* Compilation and tests on Drone.io and GitHub Actions
* Regular code audits for security

=== Nomenclature

Various names have been used historically to refer to different flavors of resource identifiers, including _URI_, _URL_, _URN_, and even _IRI_.
Over time, the distinction between URIs and URLs has disappeared when discussed in technical documents and informal works.
In this library we use the term _URL_ to refer to all strings which are valid according to the top-level grammar rules found in _rfc3986_.

==== ABNF

This documentation uses the
https://en.wikipedia.org/wiki/Backus%E2%80%93Naur_form[Augmented Backus-Naur Form]
(ABNF) notation of
https://datatracker.ietf.org/doc/html/rfc5234[rfc5234]
to specify particular grammars used by algorithms and containers.
While a complete understanding of the notation is not a requirement for using the library, it may help for an understanding of how valid components of URLs are defined.
In particular, this is of interest to users who wish to compose parsing algorithms using the combinators provided by the library.

=== Visual Studio Solution Generation

[source,bash]
----
cmake -G "Visual Studio 17 2022" -A Win32 -B bin -D BUILD_TESTING -D CMAKE_TOOLCHAIN_FILE=cmake/toolchains/msvc.cmake
cmake -G "Visual Studio 17 2022" -A x64 -B bin64 -D BUILD_TESTING -D CMAKE_TOOLCHAIN_FILE=cmake/toolchains/msvc.cmake
----

== Quick Look

=== Integration

[NOTE]
====
Sample code and identifiers used throughout are written as if the following declarations are in effect:

[source,c++]
----
#include <boost/url.hpp>
using namespace boost::urls;
----
====

We begin by including the library header file which brings all the symbols into scope.

[source,c++]
----
#include <boost/url.hpp>
----

Alternatively, individual headers may be included to obtain the declarations for specific types.

Boost.URL is a compiled library.
You need to install binaries in a location that can be found by your linker and link your program with the Boost.URL built library.
If you followed the [@http://www.boost.org/doc/libs/release/more/getting_started/index.html Boost Getting Started]
instructions, that's already been done for you.

For example, if you are using CMake, you can use the following commands to find and link the library:

[source,cmake]
----
find_package(Boost REQUIRED COMPONENTS url)
target_link_libraries(my_program PRIVATE Boost::url)
----

=== Parsing

Say you have the following URL that you want to parse:

[source,c++]
----
boost::core::string_view s = "https://user:pass@example.com:443/path/to/my%2dfile.txt?id=42&name=John%20Doe+Jingleheimer%2DSchmidt#page%20anchor";
----

In this example, `string_view` is an alias to `boost::core::string_view`, a
`string_view` implementation that is implicitly convertible from and to `std::string_view`.

You can parse the string by calling this function:

[source,c++]
----
boost::system::result<url_view> r = parse_uri( s );
----

The function _parse_uri_ returns an object of type `result<url_view>`
which is a container resembling a variant that holds either an error or an object.
A number of functions are available to parse different types of URL.

We can immediately call `result::value` to obtain a `url_view`.

[source,c++]
----
url_view u = r.value();
----

Or simply

[source,c++]
----
url_view u = *r;
----

for unchecked access.

When there are no errors, `result::value`
returns an instance of _url_view_, which holds the parsed result.

`result::value` throws an exception on a parsing error.
Alternatively, the functions `result::has_value` and `result::has_error` could also be used to check if the string has been parsed without errors.

[NOTE]
====
It is worth noting that _parse_uri_ does not allocate any memory dynamically.
Like a `string_view`, a _url_view_ does not retain ownership of the underlying string buffer.

As long as the contents of the original string are unmodified, constructed URL views always contain a valid URL in its correctly serialized form.

If the input does not match the URL grammar, an error code is reported through _result_ rather than exceptions.
Exceptions only thrown on excessive input length.
====

=== Accessing

Accessing the parts of the URL is easy:

[source,c++]
----
url_view u( "https://user:pass@example.com:443/path/to/my%2dfile.txt?id=42&name=John%20Doe+Jingleheimer%2DSchmidt#page%20anchor" );
assert(u.scheme() == "https");
assert(u.authority().buffer() == "user:pass@example.com:443");
assert(u.userinfo() == "user:pass");
assert(u.user() == "user");
assert(u.password() == "pass");
assert(u.host() == "example.com");
assert(u.port() == "443");
assert(u.path() == "/path/to/my-file.txt");
assert(u.query() == "id=42&name=John Doe Jingleheimer-Schmidt");
assert(u.fragment() == "page anchor");
----

URL paths can be further divided into path segments with the function `url_view::segments`.

Although URL query strings are often used to represent key/value pairs, this interpretation is not defined by _rfc3986_.
Users can treat the query as a single entity.
_url_view_ provides the function
`url_view::params` to extract this view of key/value pairs.

[source,c++]
----
for (auto seg: u.segments())
std::cout << seg << "\n";
std::cout << "\n";

for (auto param: u.params())
std::cout << param.key << ": " << param.value << "\n";
std::cout << "\n";
----

The output is:

[source]
----
path
to
my-file.txt

id: 42
name: John Doe Jingleheimer-Schmidt

----

These functions return views referring to substrings and sub-ranges of the underlying URL.
By simply referencing the relevant portion of the URL string internally, its components can represent percent-decoded strings and be converted to other types without any previous memory allocation.

[source,c++]
----
std::string h = u.host();
assert(h == "example.com");
----

A special `string_token` type can also be used to specify how a portion of the URL should be encoded and returned.

[source,c++]
----
std::string h = "host: ";
u.host(string_token::append_to(h));
assert(h == "host: example.com");
----

These functions might also return empty strings

[source,c++]
----
url_view u1 = parse_uri( "http://www.example.com" ).value();
assert(u1.fragment().empty());
assert(!u1.has_fragment());
----

for both empty and absent components

[source,c++]
----
url_view u2 = parse_uri( "http://www.example.com/#" ).value();
assert(u2.fragment().empty());
assert(u2.has_fragment());
----

Many components do not have corresponding functions such as
`has_authority` to check for their existence.
This happens because some URL components are mandatory.

When applicable, the encoded components can also be directly accessed through a `string_view` without any need to allocate memory:

[source,c++]
----
std::cout <<
    "url       : " << u                     << "\n"
    "scheme    : " << u.scheme()            << "\n"
    "authority : " << u.encoded_authority() << "\n"
    "userinfo  : " << u.encoded_userinfo()  << "\n"
    "user      : " << u.encoded_user()      << "\n"
    "password  : " << u.encoded_password()  << "\n"
    "host      : " << u.encoded_host()      << "\n"
    "port      : " << u.port()              << "\n"
    "path      : " << u.encoded_path()      << "\n"
    "query     : " << u.encoded_query()     << "\n"
    "fragment  : " << u.encoded_fragment()  << "\n";
----

The output is:

[source]
----
url : https://user:pass@example.com:443/path/to/my%2dfile.txt?id=42&name=John%20Doe+Jingleheimer%2DSchmidt#page%20anchor
scheme : https
authority : user:pass@example.com:443
userinfo : user:pass
user : user
password : pass
host : example.com
port : 443
path : /path/to/my%2dfile.txt
query : id=42&name=John%20Doe+Jingleheimer%2DSchmidt
fragment : page%20anchor
----

=== Percent-Encoding

An instance of `decode_view` provides a number of functions to persist a decoded string:

[source,c++]
----
decode_view dv("id=42&name=John%20Doe%20Jingleheimer%2DSchmidt");
std::cout << dv << "\n";
----

The output is:

[source]
----
id=42&name=John Doe Jingleheimer-Schmidt
----

`decode_view` and its decoding functions are designed to perform no memory allocations unless the algorithm where its being used needs the result to be in another container.
The design also permits recycling objects to reuse their memory, and at least minimize the number of allocations by deferring them until the result is in fact needed by the application.

In the example above, the memory owned by `str` can be reused to store other results.
This is also useful when manipulating URLs:

[source,c++]
----
u1.set_host(u2.host());
----

If `u2.host()` returned a value type, then two memory allocations would be necessary for this operation.
Another common use case is converting URL path segments into filesystem paths:

[source,c++]
----
boost::filesystem::path p;
for (auto seg: u.segments())
p.append(seg.begin(), seg.end());
std::cout << "path: " << p << "\n";
----

The output is:

[source]
----
path: "path/to/my-file.txt"
----

In this example, only the internal allocations of `filesystem::path` need to happen.
In many common use cases, no allocations are necessary at all, such as finding the appropriate route for a URL in a web server:

[source,c++]
----
auto match = [](
std::vector<std::string> const& route,
url_view u)
{
auto segs = u.segments();
if (route.size() != segs.size())
return false;
return std::equal(
route.begin(),
route.end(),
segs.begin());
};
----

This allows us to easily match files in the document root directory of a web server:

[source,c++]
----
std::vector<std::string> route =
{"community", "reviews.html"};
if (match(route, u))
{
handle_route(route, u);
}
----

=== Compound elements

The path and query parts of the URL are treated specially by the library.
While they can be accessed as individual encoded strings, they can also be accessed through special view types.

This code calls `encoded_segments` to obtain the path segments as a container that returns encoded strings:

[source,c++]
----
segments_view segs = u.encoded_segments();
for( auto v : segs )
{
std::cout << v << "\n";
}
----

The output is:

[source]
----
path to my-file.txt
----

As with other `url_view` functions which return encoded strings, the encoded segments container does not allocate memory.
Instead, it returns views to the corresponding portions of the underlying encoded buffer referenced by the URL.

As with other library functions, `decode_view` permits accessing elements of composed elements while avoiding memory allocations entirely:

[source,c++]
----
segments_view segs = u.encoded_segments();
for( pct_string_view v : segs )
{
decode_view dv = *v;
std::cout << dv << "\n";
}
----

The output is:

[source]
----
path to my-file.txt
----

Or with the encoded query parameters:

[source,c++]
----
params_encoded_view params_ref = u.encoded_params();

for( auto v : params_ref )
{
    decode_view dk(v.key);
    decode_view dv(v.value);
    std::cout <<
        "key = " << dk <<
        ", value = " << dv << "\n";
}
----

The output is:

[source]
----
key = id, value = 42
key = name, value = John Doe
----

=== Modifying

The library provides the containers `url` and `static_url` which supporting modification of the URL contents.
A `url` or `static_url` must be constructed from an existing `url_view`.

Unlike the `url_view`, which does not gain ownership of the underlying character buffer, the `url` container uses the default allocator to control a resizable character buffer which it owns.

[source,c++]
----
url u = parse_uri( s ).value();
----

On the other hand, a `static_url` has fixed-capacity storage and does not require dynamic memory allocations.

[source,c++]
----
static_url<1024> su = parse_uri( s ).value();
----

Objects of type `url` are https://en.cppreference.com/w/cpp/concepts/regular[std::regular].
Similarly to built-in types, such as `int`, a `url` is copyable, movable, assignable, default constructible, and equality comparable.
They support all the inspection functions of `url_view`, and also provide functions to modify all components of the URL.

Changing the scheme is easy:

[source,c++]
----
u.set_scheme( "https" );
----

Or we can use a predefined constant:

[source,c++]
----
u.set_scheme_id( scheme::https ); // equivalent to u.set_scheme( "https" );
----

The scheme must be valid, however, or an exception is thrown.
All modifying functions perform validation on their input.

* Attempting to set the URL scheme or port to an invalid string results in an exception.
* Attempting to set other URL components to invalid strings will get the original input properly percent-encoded for that component.

It is not possible for a `url` to hold syntactically illegal text.

Modification functions return a reference to the object, so chaining is possible:

[source,c++]
----
u.set_host_ipv4( ipv4_address( "192.168.0.1" ) )
    .set_port_number( 8080 )
    .remove_userinfo();
std::cout << u << "\n";
----

The output is:

[source]
----
https://192.168.0.1:8080/path/to/my%2dfile.txt?id=42&name=John%20Doe#page%20anchor
----

All non-const operations offer the strong exception safety guarantee.

The path segment and query parameter containers returned by a `url` offer modifiable range functionality, using member functions of the container:

[source,c++]
----
params_ref p = u.params();
p.replace(p.find("name"), {"name", "John Doe"});
std::cout << u << "\n";
----

The output is:

[source]
----
https://192.168.0.1:8080/path/to/my%2dfile.txt?id=42&name=Vinnie%20Falco#page%20anchor
----

=== Formatting

Algorithms to format URLs construct a mutable URL by parsing and applying arguments to a URL template.
The following example uses the `format`
function to construct an absolute URL:

[source,c++]
----
url u = format("{}://{}:{}/rfc/{}", "https", "www.ietf.org", 80, "rfc2396.txt");
assert(u.buffer() == "https://www.ietf.org:80/rfc/rfc2396.txt");
----

The rules for a format URL string are the same as for a `std::format_string`, where replacement fields are delimited by curly braces.
The URL type is inferred from the format string.

The URL components to which replacement fields belong are identified before replacement is applied and any invalid characters for that formatted argument are percent-escaped:

[source,c++]
----
url u = format("https://{}/{}", "www.boost.org", "Hello world!");
assert(u.buffer() == "https://www.boost.org/Hello%20world!");
----

Delimiters in the URL template, such as `":"`, `"//"`, `"?"`, and `"#"`, unambiguously associate each replacement field to a URL component.
All other characters are normalized to ensure the URL is valid:

[source,c++]
----
url u = format("{}:{}", "mailto", "someone@example.com");
assert(u.buffer() == "mailto:someone@example.com");
assert(u.scheme() == "mailto");
assert(u.path() == "someone@example.com");
----

[source,c++]
----
url u = format("{}{}", "mailto:", "someone@example.com");
assert(u.buffer() == "mailto%3Asomeone@example.com");
assert(!u.has_scheme());
assert(u.path() == "mailto:someone@example.com");
assert(u.encoded_path() == "mailto%3Asomeone@example.com");
----

The function `format_to` can be used to format URLs into any modifiable URL container.

[source,c++]
----
static_url<50> u;
format_to(u, "{}://{}:{}/rfc/{}", "https", "www.ietf.org", 80, "rfc2396.txt");
assert(u.buffer() == "https://www.ietf.org:80/rfc/rfc2396.txt");
----

As with `std::format`, positional and named arguments are supported.

[source,c++]
----
url u = format("{0}://{2}:{1}/{3}{4}{3}", "https", 80, "www.ietf.org", "abra", "cad");
assert(u.buffer() == "https://www.ietf.org:80/abracadabra");
----

The `arg` function can be used to associate names with arguments:

[source,c++]
----
url u = format("https://example.com/~{username}", arg("username", "mark"));
assert(u.buffer() == "https://example.com/~mark");
----

A second overload based on `std::initializer_list`
is provided for both `format` and `format_to`.

These overloads can help with lists of named arguments:

[source,c++]
----
boost::core::string_view fmt = "{scheme}://{host}:{port}/{dir}/{file}";
url u = format(fmt, {{"scheme", "https"}, {"port", 80}, {"host", "example.com"}, {"dir", "path/to"}, {"file", "file.txt"}});
assert(u.buffer() == "https://example.com:80/path/to/file.txt");
----

== Documentation

The complete library documentation is available online at https://www.boost.org/doc/libs/master/libs/url/doc/html/index.html[boost.org].

== Acknowledgments

This library wouldn't be where it is today without the help of
https://github.com/pdimov[Peter Dimov], for design advice and general assistance.

== License

Distributed under the Boost Software License, Version 1.0. (See accompanying file LICENSE_1_0.txt or copy at
https://www.boost.org/LICENSE_1_0.txt)

